Autoconfigured Slave zones get same (master) IP for all dns servers

I have the autoconfigured slave zones set up, using 3 servers (1 pro master, 2 gpl slaves). I can add a virtual server, and it creates the domains, but it gives the master IP address to all NS records instead of supplying the correct IP per server record. ie: the NS1 record is correct, but NS2 and NS3 (the two slaves) records show the same IP as NS1. How do I tell it the correct IP's to use for the ns2 and ns3 records?

Status: 
Closed (fixed)

Comments

If you check the zone file for the domain, what hostnames are set for the NS records?

Are they all the same, or are they different but resolve to the same IP?

Screenshot attached. It shows that the NS records have only ns2 and ns3 (ns1 should also be NS). ns1 is SOA. As for A records, it does not include an A record for ns1, and both ns2 and ns3 are assigned the ns1 (master) IP address.

Check at System Settings -> Server Templates -> Default Settings -> BIND DNS Domain -> BIND DNS records for new domains that the records for ns2 and ns3 have the correct IP addresses. It looks from that screenshot like you might have set them to ${IP} instead of the correct IPs.

The "BIND DNS Records for New Domains" box is empty.

Ok .. so what is shown at Webmin -> Servers -> BIND DNS Server -> Cluster Slave Servers ?

ns2.ezhostr.com and ns3.ezhostr.com. Screenshot attached.

You need to correct the IPs for ns2 and ns3 in the ezhostr.com domain in Virtualmin.

Then when any new domains are created in future, they will use the correct IPs..

Thanks, I got it to work by doing this and adding an A record for ns1.ezhostr.com, as well as checking the "Add nameserver record for this system" option in the server template. Now new domains are created with all 3 NS records. Thanks for your help.

Automatically closed -- issue fixed for 2 weeks with no activity.