Change of External IP does not update Cluster Slave

Submitted by ernestneo on Sun, 06/02/2013 - 21:46

After changing a Virtual Server's External IP configuration, the Cluster Slave DNS servers does not reflect the new External IP Address as the Master Server IP.

This breaks the DNS Slaves.

Status: 
Active

Comments

Submitted by JamieCameron on Sun, 06/02/2013 - 23:00

Did the primary IP of the system change in this case? Normally changing the external IP of a domain has no effect on the system's primary address, and so there is no need to update the master IP.

Submitted by ernestneo on Tue, 06/04/2013 - 03:13

The domain's external IP and the System primary address is the same in this case.

For instance.

Old System External IP: 123.1.1.1 Old Domain External IP: 123.1.1.1

Slave DNS Master Server: 123.1.1.1

New System External IP: 123.2.2.2 New Domain External IP: 123.2.2.2

Slave DNS Master Server: 123.1.1.1

Submitted by JamieCameron on Tue, 06/04/2013 - 13:05

I think what Virtualmin should really do in this case is detect when your eth0 IP address has changed, and updated slave master nameservers to match. I'll look into fixing this.

Submitted by JamieCameron on Sat, 06/08/2013 - 13:55

This will be added in the next Virtualmin release.

Submitted by zervin on Thu, 06/20/2013 - 09:28

I think I have run into the same issue. I was in the process of migrating the master hosting server to a new network+external ip address. The result was that I can no longer push updates for the actual domains because the master server is no longer accurate in each zone. Has this update been pushed? or is there a better way to force the masters to update in each zone than manually editing each zone?

My problem is somewhat compounded by the fact that some of the dns servers need to be moved as well. It may be a chicken an egg situation where I need to move the master before slave or vice versa.

Submitted by JamieCameron on Thu, 06/20/2013 - 14:19

The work-around for this in the short term is to remove all the slave domains, and then re-add them.

This is best done using Virtualmin's command line API, with a command like :

virtualmin modify-dns --domain example.com --remove-slave xxx
virtualmin modify-dns --domain example.com --add-slave xxx

where xxx is the hostname of the slave DNS server, as shown at Webmin -> Servers -> BIND DNS Server -> Cluster Slave Servers.