nameservers not reflecting whats in zone records

simeon

• April 18, 2017 22:56

This is a strange one. I've been running whm server for about 10 years and haven't run into this before. I've got three whm servers, all in a dns cluster (lets call them server1, server2, and server3). All are running whm 64 I moved a few sites from from server2 to server3 on the weekend (2, almost 3 days ago). In the zone records, I can see that the sites updated with their new ip addresses. TTLs are set to 4 hours. The dns however, has not updated. By checking 3rd party sites like whatsmydns.net, or mxtoolbox, I can see the domains still resolving to the old IP address. In fact, if I do an nslookup in the terminal on any of the servers, that returns the old address as well. I successfully moved sites a couple of weeks ago, so this seems to be a recent issue. I'm not sure where to look. simon

• 

  cPanelMichael

  • April 19, 2017 19:18

  In the zone records, I can see that the sites updated with their new ip addresses. TTLs are set to 4 hours. The dns however, has not updated.

  
  Hello, Have you verified the correct DNS entries are utilized on all services in the cluster? If so, try browsing to "WHM Home " DNS Functions " Synchronize DNS Records" and use "Synchronize one zone to all servers" for one of the affected domain names. Thank you.

  0
• 

  simeon

  • April 19, 2017 21:22

  Just tried that. No change. Zone records in whm are good on all servers, the nslookup returns the incorrect ip though.

  0
• 

  cPanelMichael

  • April 19, 2017 21:36

  Hello, Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you.

  0
• 

  simeon

  • April 19, 2017 21:39

  8393209

  0
• 

  cPanelMichael

  • May 04, 2017 18:01

  Hello, To update, here's a quote from the support ticket explaining how this works: When using DNS clustering, an account can not exist on multiple servers as it will cause such conflicts. The best way to handle migrating accounts when using DNS clustering is to disable clustering on both servers, migrate the account, then re-enabling the cluster after the account is on the destination server and removed from the source.
  Thank you.

  0

Please sign in to leave a comment.