Tinus Nijmeijers wrote:
just wanted to run this by some people more knowledgeable than myself. please tell me if I'm wrong.-at the registrar: change the IP of dns0.domain.net to the IP of NEW -change the zone files on OLD and NEW to reflect the move to the new IP-wait a couple of days for everyone to catch up. -take OLD down.
(Personal opinion being spoken here)This is the way 90% of the 'Net does renumbering, and it's wrong, or at least not nearly as effective as better ways which aren't that hard to do.
Treat registrar changes (i.e. which DNS servers to use) and host changes (i.e. what's the ip address of www.somewhere.com) as two totally separate events, as follows:
Host changes:1) As someone else pointed out, lower the TTL values for any/all hosts that are going to move. This needs to be done at least 2x(current TTL) before the move to get maximum consistency. 2) Move (renumber) the hosts, change the host records in the zone file(s), and restore the TTL to your operational default. 3) Aside from broken resolvers, the transition will only take as long as the short TTL you used temporarily, and/or the time needed to successfully renumber your hosts. THIS DOES NOT TAKE 2-3 DAYS, unless it's poorly executed.
Registrar changes:1) Be sure to have a new DNS server while leaving the existing DNS server operational. 2) Set up all relevant zone files on the new DNS server with the proper host information (i.e. it could be a secondary/slave from the old DNS server, or just scp the zone files over, etc.).
3) Make the changes at the registrar.4) If you need to change any zone file information, be sure the change occurs on both old and new DNS servers. 5) No matter which GTLD server and which SLD server a client's resolver contacts, it'll always get the right information.