Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

We're registered our domain at Network Solutions. They went down a month ago and our DNS was down. We're trying to find a way to mitigate this issue. Our domain stops resolving and we have to send our customers to our our IP address and then the SSL cert gives them a warning. In short, it's annoying.

Of course, we can move to Namecheap or Godaddy, but we would still run into this issue....the bottle neck.


share|improve this question
Can you please clarify the warning message? – GioMac Aug 30 '13 at 0:17
It might be a good idea to setup your domain name with two or more DNS providers so that if one goes down, you'll still have one. – ponsfonze Aug 30 '13 at 0:31
Just read this:… and follow the part of "further failover measures". Basically, like Zoredache said – TheCleaner Aug 30 '13 at 0:48

You don't have to host your DNS with the registrar you use. Registering the zone, and acting as the host for the zone are two separate services. There are many services in the world you can pay for to host your zone, or act as secondaries for your zone.

For example one organization I know has their domain registered through Godaddy, and zone is primarily hosted on, but they also have Godaddy's Premium DNS server so that Godaddy is a secondary for the zone as well. Which means their zone is both on Godaddy, and systems.

share|improve this answer

Run your own. You'll learn a ton in the process.

share|improve this answer
Including learning that it may be better left to a third-party who dedicates themselves to running a good DNS infrastructure. – ceejayoz Aug 30 '13 at 2:28
Possibly. I've done it myself for a long time without issue. That said, I'm currently using Route 53 for my new dayjob. I like DNS, so that's my bias. Running some web UI somewhere will not teach you very much. – dmourati Aug 30 '13 at 2:46
SF is a site for sysadmins, so I don't think there's anything wrong with "do it yourself". If all we do is advise people to outsource, what are we? Running your whole DNS setup is probably not something you'd want to do on day one, but you could run a single DNS secondary on a custom VPS (say) with fairly small risk, and you would, as dmourati suggests, learn a bunch about how the DNS works in the process. – MadHatter Aug 30 '13 at 5:40

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.