In the old days of setting up reseller accounts with shared hosting services like HostGator, it was simple to set up "Private Nameservers" by (after having pointed the DNS entries to the hosting company's DNS servers) going to the registrar and setting A records for the NS records. My question is, can you do the same thing when you've pointed your DNS at Amazon Route53 (and are using the AWS ecosystem for hosting/servers/etc)?

This tutorial demonstrates what I'm talking about:


For GoDaddy specifically (which I'm not using, but many are familiar with): http://support.hostgator.com/articles/hosting-guide/lets-get-started/dns-name-servers/setting-up-private-name-servers-with-hostgatorenom

It involves registering, NS A records, and DNS glue. But I suspect in the case of this shared hosting, some magic was set up on the hosting company's DNS server side. What about in the case of Route53?

In short, when doing a WHOIS lookup on my domain, I don't want the four AWS/Route53 FQDMs showing as the DNS records. Though those ARE the DNS point, I want ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com, and ns4.mydomain.com, respectively, to display on a WHOIS lookup.

  • 1
    If I'm understanding your last paragraph correctly, you will need to keep track of Amazon's name server IP addresses yourself and change your glue records every time Amazon make a change. I don't know how often they make changes to those IP addresses. – Ladadadada Dec 21 '13 at 22:38

Yes, as of Nov 2014 you can do this, here is how:


| improve this answer | |

This blog post explains a setup where you combine Route 53 with on-premise DNS using Unbound: https://aws.amazon.com/blogs/security/how-to-set-up-dns-resolution-between-on-premises-networks-and-aws-by-using-unbound/

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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