Getting ready to switch ISP - minimalize dns replication issue

Have multiple web/email/app servers that are all associated with external ip addresses that will change when i go to a different provider.  We handle DNS in-house.  The registrar currently makes reference to my 2 name servers on my current provider block.  The new provider will give me our ip address up front so i can make inital configurations.  My idea was to create 2 additional name servers  with the new ip addresses prior to the actual rollout so as to replicate accross.

proposed idea =
current: = online = online = offline = offline

day of rollout: = offline = offline = online = online

ns1-ns4 would all be replicated accross the internet but only 50% available at any given time.  the day of rollout i would make all the config changes on my local dns to reflect the new ip addresses once the new provider is live - a step i must take because i only have the 2 name servers.  ns1 will become ns3 and ns2 will become ns4.

Unless there is a much easier way to do this....but i have been instructed to change ISP with at most 1 hour of downtime / can't wait the 24-36 hour dns replication time.

Ideas or thougts?
Who is Participating?
As I understand it, there are a couple of issues here.  First, you want DNS outages to be kept to a minimum, second, you need to get everything moved over to the new IPs with minimum downtime.

Regarding the first point, your idea to set up two new servers is a fine one though a bit risky - especially if there are any problems during the switchover.  If everything goes smoothly the day of the changeover, you're good - if not, there could be problems.

 Assuming you'll either have the new ISP up ahead of time or can keep the old ISP a bit after the transition (a day of overlap should be plenty, I would not replicate ns3/ns4 (the new servers) with ns1/ns2 (the old ones).  Instead, I'd load only the DNS information needed to resolve hosts once assigned to the new IPs on ns3/ns4.  Essentially, you'll still have 2 pairs of server and only one pair online at any given time.  That way, as soon as you bring the new IPs online, the new DNS servers will be there and waiting with only the correct information (no stale records from old IPs).

Be sure you register all 4 DNS servers with your registrar well before the swap so that all 4 are offered as authoritative even though only 2 will be available at any time.

As for reducing the replication time once you make the change, a few days (or more) before you are ready to make the transfer, reduce the TTLs on all records (including the SOA) on the old servers to less than 30 minutes.  Doing it well in advance will make certain that the new TTL will have propagated to any servers on the internet that may have cached records and those servers will know to expire the cache quickly and look for new info.  That way when you do make the swap, the new addresses will be picked up quickly.

This will increase DNS traffic quite a bit.  If that will be a problem, set up an additional server with a third party (even if only temporarily) and make it the primary for your domain with your registrar.

Hope this helps!
Andrej PirmanCommented:
The TTL idea is what I use each time I switch anything and needs to be propagated quickly, so it is proven to be good.
Where I see a problem is that you host your DNS in-house, which means, when switching ISP, your DNS will be in dark, too, so your parent DNS at your registrar will fail lookup, and DNS changes will not even begin to propaginate.
To workaround, as Mdcsea already suggested, it is a MUST TO setup external DNS, not only for the switching period, but also for later use. I suggest you to use free DNS service at, where you may setup Secondary DNS for your main domain, which hosts your DNS.
For example, if you use your own DNS names
setup Primary DNS for in I say *primary* because if it is Secondary, you won't have a chance to edit zone records to point to new IP, so temporarily zone *must* be Primary.
After you make a switch, you may convert the zone to secondary with a simple click.

bingbooAuthor Commented:
The new provider has recommended that we maintain just the one Name Server on the new backbone with the updated new ip addresses on the day of transition and leave one web server temporarily behind on the old ISP backbone that will answer name resolution hits to the old IP address.  This should take care of all websites issues however I will still need to publish secondary mx records several days prior to rollout.
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

Andrej PirmanCommented:
Fine, so here are your steps:
1.) Add secondary MX records for your domain with higher number (higher number=lower priority MX)
1b.) If you want to speed up transition process, lower TTL values, also SOA Time To Live, in your old DNS zone settings. Lower TTL down from default 24 or 48 hours to an hour or two, or even less, but an hour is enough.
2.) Setup your new server and make sure all is working fine, all websites, all databases, all mails
3.) Setup your new DNS, and, if it is on YOUR domain AND will have different name as your old DNS servers, don't forget to register those new DNS server name, for example,, at your domain registrar and tell them it is for DNS server! Registering a sub-domain, for example, as DNS server, needs some extra steps at your registrar, yhich will register this name in DNS namespace.
4.) Test your new server from your home computer, temporarily assigning your new DNS server's IP as your only DNS server for your home computer. Doing so, you will emulate as your new server is already in production, but only you will see it.
5.) When everything works fine, you are ready to either:
- change NAMEs of your dns servers at your registrar, if your old DNS was, for example,, and your new DNS is
- or change IPs of your DNS servers, if your old and new DNS servers will have the same name, only IP will be different
6.) After TTL time your transfer will be visible to whole internet and you are done. Hopefully with no problems.
bingbooAuthor Commented:
Sorry for the delay, I only have one remaining question.  Can I publish a  Name Server even though it will be offline for a week or so?  As long as I have at least one Name server online that can correctly resolve I should be ok yes?
Yes, you may have multiple nameservers - even if they are not all active.  The nameservers that are offline will be listed as 'lame' nameservers (meaning they are not responsive) until they are brought online.

When you are ready to make your transition, simply shut down the servers that contain the old information.  Remember though, if you don't set the TTLs down to a low number shortly before the transition you will experience a latency as cached DNS records expire on servers across the internet.
bingbooAuthor Commented:
Thank you both very much and sorry for the delay.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.