Account migration to another server in the same dns cluster

[rockeby]

Hi,

I've got 2 cPanel/WHM servers (cloud1.server.com and cloud2.server.com) and 2 cPanel DNSonly servers (ns1.server.com and ns2.server.com).

This is the way I configured the 2 servers in the clusters:


cloud1.server.com
--> ns1.server.com. (synchronize changes)
-->ns2.server.com (synchronize changes)


cloud1.server.com
--> ns1.server.com (synchronize changes)
-->ns2.server.com (synchronize changes)

When I transferred the the account from cloud1.server.com to cloud2.server.com the account on cloud1.server.com got suspended but the domain was not reachable. When I pinged the domain it actually continued to point to cloud1.server.com and on the browser it would return the message "The account has been moved". Then I decided to cancel the account on cloud1.server.com and at that point it was not reachable at all via the browser.

I made sure that the DNS zone were not cancelled and in fact they were there with the domain pointing to the new server cloud2.server.com. I cleared all my browser cache and even tried with an anonymous browser and the domain was yet not reachable, but still pointing to the old server cloud1.server.com.

Only about after a couple of hours the domain was reachable and pointing to the new server cloud2.server.com.

Is it normal that it takes so long to update the propagation even if the account was transferred in the same clusters without changing any name servers? Should not be almost instantaneous the update? Is my configuration wrong?

Thanks in advance for the help

 

[cPRex]

Hey there! That sounds correct to me - even though the nameservers didn't change, the IP address did, so it would need to go through full propagation like any other DNS change.

 

[rockeby]

Hey there! That sounds correct to me - even though the nameservers didn't change, the IP address did, so it would need to go through full propagation like any other DNS change.

Great, thank you for your explanation. Many thanks.

 

[ffeingol]

As a "best practice" you'd want to lower the TTL (something like 1200 or 20 minutes) well before the migration. Then when you migrate the DNS will 'update' in 20 minutes vs. the default cPanel 14400 (or 4 hours).