My domain registrar is Company A and we use two of their nameservers for DNS. We host our own server hardware in a datacenter that's not affiliated with Company A. Everything about Company A sucks. So we've set up a new account on DNSmadeeasy.com and I copied all our A, MX, and CNAME records over (they take care of SOA and NS). Now, when I log in to my registrar's panel and switch the name servers from theirs to DNSME, are we going to experience any sort of interruption in service?

My initial thought it no, we shouldn't. As with any DNS changes, propagation can take up to 72 hours, but if certain name servers don't have the updated zone files yet, they'll most likely used cached information which is all the same (because NO IP addresses are changing... it's an exact replica).

So what do you think? Should I go ahead and make the change or should I pick a scheduled date and notify clients that they may experience connectivity issues within the 72 hour window?


Nearly 72 hours have passed and we didn't even have as much as a hiccup. Throughout the last 72 hours I've used nslookup to query several different servers for my NS records and it took about 48 hours for all of them to show the new name servers. The whois information changed almost immediately. So bottom line for anyone that has the same worries as I did, as long as the new DNS providers have the exact same zone information, you won't have any issues.

4 Answers 4


No, as long as both sets of nameservers have the same records you'll experience no downtime.

  • Note that changing from a registrar that uses DNSSEC to a registrar that doesn’t support it, you’ll get downtime if you don’t remember to disable DNSSEC and waiting 24 hours before switching. I hit this issue when trying to migrate from google domains to siteground. Feb 4 at 7:38

There should be no downtime if records are the same. I always like to confirm both records are the same by doing lookups directly against the DNS made easy nameservers.

You can use an online tool for this or you can use

dig @ns#.dnsmadeeasy.com domain.com A


To confirm each record.

  • I did this and still experienced downtime, probably because of the same reason stated by jlmt in his answer
    – Grodriguez
    Sep 12, 2014 at 12:55

This is something to be slightly wary of in my recent experience.

We were previously using Company A, who sucks. They were the domain registrar and the DNS host for ourcompanydomain.com.

We set up the same DNS A and MX records for ourcompanydomain.com with Company B.

We then changed the nameservers for ourcompanydomain.com in Company A's control panel to ns.companyb.com and ns2.companyb.com, assuming that because the same DNS entries existed in both places, the swap would be seamless.

However, shortly afterwards mail to [email protected] went down in various places. I'm no DNS expert, but my assumption is that Company A stopped responding to DNS lookups for our domain before everything had propagated.

Bottom line - unless you have full control of the process, I'd make sure you have a contingency plan for possible downtime when changing nameservers.

  • 1
    The moral of that story being that one should NEVER use the registrar's nameservers.. Aug 16, 2014 at 14:36
  • 2
    Had exactly the same problem. In my case "Company A" was 1and1.
    – Grodriguez
    Sep 12, 2014 at 12:56
  • So in other words your previous Nameservers had the DNS records removed before propagation had completed. You mentioned "I'm no DNS expert" are you sure there wasn't some kind of a "Delete records" checkbox that you mistakenly checked when saving your changes or something?
    – Jay
    May 23, 2018 at 17:02

Yes and no. It won't cause any downtime if both servers (the old and the new) are running, but what I will do is cause some discrepancies.

What I mean is that if the DNS of one of your users has not updated to the new nameservers, they will be on the old server. Depending on what your running, this could be good or bad. And on the other hand, some DNS servers may be updated and pointing to your new server.

Essentially, you need to make sure you have both servers up for at least two days (just in case - some DNS servers are very slow at updating) until you take the old server down completely.

I'd at least put in warning at least five hours before you make the change, just in case. :)

  • 1
    He's just talking about switching from one pair of nameservers to the other. He said he copied the records over to the new nameservers, so in this case there is going to be no downtime. It doesn't matter which server the client is querying, they will get the same data back.
    – devicenull
    Dec 10, 2011 at 5:55
  • True, but let's say if the OP is running a Minecraft server and people connect to the server with the old server's IP. You'll run into some problems. As I'm not sure what the OP is running, you can never assume it's only a web server... Dec 10, 2011 at 18:02
  • 1
    People will be connecting to the same IP either way.
    – ceejayoz
    Dec 10, 2011 at 18:52
  • Thanks Taylor, but what I'm running is irrelevant because none of my IPs are changing. There is no 'old server'. Just the nameservers that my registrar recognizes as the official dns authority for my zone changed.
    – Safado
    Dec 12, 2011 at 20:55
  • 1
    Ah ha. Sorry about that. Misunderstood the question. Now it makes sense. Dec 12, 2011 at 21:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .