• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 318
  • Last Modified:

Secondary nameserver is not updating from Primary DNS server

We have recently moved a website from server A to server B. I have updated the zone files on the primary nameserver, but the secondary nameserver is not updating to reflect the changes. The new zone file has a newer serial number than the old, but it still will not update. Can I force the slave to update? Any other ideas?

THanks
0
verbal11
Asked:
verbal11
  • 4
  • 2
  • 2
1 Solution
 
BarthaxCommented:
Simple resolution is to delete the zone file on the slave server and send a HUP signal to the dns daemon - it should restart and pull the new file down.
0
 
marxyCommented:
try

/etc/init.d/named reload

it will be forced named to reload his databases and send notation to secondaries.
0
 
verbal11Author Commented:
/etc/init.d/named reload

returns "Hangup"

deleting the zone file on the slave and restarting dns does not recreate the zone file on the slave. It does however create a 0 byte file with the same zone file name but with a 6 digit random character extension. (ie. domain.com.7Neaht)
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
verbal11Author Commented:
and by the way....thanks for your assistance with this.
0
 
verbal11Author Commented:
more information:

My messages log shows this line:
Mar  9 14:10:42 mobydick named-xfer[21647]: connect(12.34.567.89) for zone domain.com failed: Connection timed out

(i've changed the IP and domain names)

What could be preventing the slave server from connecting to the master server?
0
 
BarthaxCommented:
Connection timed out suggests either that it did connect to 12.34.567.89 but didn't get a timely response or that it attempted to connect but the connection was not established in time.  In the first instance you should check the logs of the primary server to find out what it thought about the connection.  In the second instance, try telnetting connecting to other services on the first server from the second server - you may have a generic network failure or it may be something specific to DNS.
0
 
marxyCommented:
maybe new primary is firewalled port tcp-53?
0
 
verbal11Author Commented:
Thanks, the port was blocked. I don't know why/when it became blocked, but I called our hosting company and had them check the port, and it was indeed closed.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now