0

This question already has an answer here:

I'm moving a bunch of sites to a new hosting service. They are explaining to me that I need to run my own DNS, which they are advising that I simply set a host name pointer at my registrar for dns1.foo.com and dns2.foo.com to the static IP address of the new virtual server. Then all the sites specify those two as their nameservers. I tried it, and it works.

I admit this is not my area of expertise but it seems to me to be a weak link to have all name resolution for these sites dependent on a host name setting at the registrar.

As an alternative, I experimented with a vanity DNS I have configured at AWS Route 53, simply adding glue records there that point new subs dns5 and dns6 to the static IP address of the server. This routing works, my test sites all resolve using those as their nameservers.

So, what is the better answer here - the simple "host name" DNS pointer at the registrar, or use my vanity DNS for the mapping, at Route 53?

marked as duplicate by HBruijn Nov 18 '16 at 7:16

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 2
    Although lots of people do so, you don't want your VPS to be the only nameserver for your domain name(s). Using your domain registrars or another DNS service typically is much more reliable and robust – HBruijn Nov 18 '16 at 7:20
  • @HBruijn - thanks, I would have never found that other question...very helpful. Also, in my case I am resolving to a single IP address so it sounds like that is bad, even with redundant nameservers - so I will fix that too. Thanks! – C C Nov 18 '16 at 12:15
  • 1
    Follow the link to the list of canonical questions back on Meta, there's a number of epic Q&A's dealing with DNS and other interesting topics as well. – HBruijn Nov 18 '16 at 12:19