Webmasters Stack Exchange is a question and answer site for pro webmasters. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The registrar I have is networksolutions.com, and for quite a while, the name servers were pointing to Site5.com, where hosting is for one of my domains. I wanted to bring DNS control back to networksolutions, so I pointed the name servers back to networksolutions and added in all my A records.

However, I noticed that the site soon became unreachable. I'm curious as to why this happened? If the domain was pointing to either the old name servers or the new ones, it would still have the proper A records and whatnot.

Is this because when I changed name servers, a request was made to delete them completely, and then the DNS servers worldwide have to wait for network solutions to send out the new ones or something?

I was hoping this would be a switch with zero downtime, such as a normal A record change.

share|improve this question
I would have expected zero downtime as well. Unless there was an error in the DNS zone at networksolutions? When you check the WhoIs record, does it show networksolutions? – w3dk Jun 19 '12 at 18:07
Do you have the same data (FQDNs and IPs) in both the old and new DNS servers? What kind of error are you getting? (e.g. no resolution, 404 error, 500 error, etc.) – Data Scavenger Jun 21 '12 at 1:10
Err didn't check the error code (doh!), but when looking up the domain in network-tools, it would give me some sort of generic error indicating that it failed to lookup the dns records for the domain. – Brian Jun 21 '12 at 13:49
So I called NS and they said that there will definitely be a downtime of around 1 to 2 hours during a name server change from one nameserver to another. Very upsetting. This must be something specific to Network Solutions. – Brian Jun 21 '12 at 13:52
up vote 0 down vote accepted

I've had trouble with "notworksolutions" regarding DNS issues. I was down for a week when transferring domains from their clasping little fingers.

I agree with w3d -- what does "whois" say? If networksolutions is listed as the nameserver, they need to fix the problem.

But "zero" downtime is perhaps unrealistic. It takes time for the root servers to be updated and for changes to percolate through the network. It might take 48-72 hours to get around. If not, perhaps some of the SOA parameters are sub-optimal.

share|improve this answer
I hate to disagree, but I think that a non-outage was a completely reasonable expectation IF the same DNS data is stored in both the old and new SOAs. I've done this myself several times. – Data Scavenger Jun 21 '12 at 1:08
Yea, if the A record is identical, I agree that there should be no downtime if the old nameserver is still functional. <p>But @Brian said he was required to delete the old nameserver, which might give "name not found" errors while the root servers were being updated. I think requiring that old nameservers be deleted was totally unreasonable in this case. – Jan Steinman Jun 22 '12 at 1:46
WHY must StackExchange remove line breaks in comments? Does it want to be FacePlant when it grows up? – Jan Steinman Jun 22 '12 at 1:48
Bleh - I think the issue was probable that the name server change was done before network solutions actually had a zone file created and pushed out. But on my second attempt, everything went smoothly. – Brian Jun 26 '12 at 1:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.