Server Fault is a question and answer site for system and network administrators. 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

I'm trying to migrate an existing domain to Amazon Route 53. I've followed the guide at:

My current DNS host is There seem to be two areas where the NS records are stored. I looked in the zone file and updated the NS entries to point to Amazon Route53. Changing those seems to have made no difference (checked via whois).

I've noticed another section in the configuration portal specifically for nameserver, but in order to change them from the default, I'm being asked to enter both the FQDN of the new name servers and also its IP address.

Amazon have not said anything about the IP address of their name servers (the "Delegation Set"), and I suppose it's simple enough to ping them and get their IPs that way. But I'm wondering if those name servers are clusters and it's not intended that I supply a single IP address for them.

Is it safe for me to just ping each of the servers in the Route 53 delegation set and use the IP addresses I see when I ping it when transferring the domain from to Route 53?

share|improve this question
up vote 1 down vote accepted

I found the answer elsewhere on Amazon's documentation site:

Some registrars only allow you to specify name servers using IP addresses; they don't allow you to specify fully qualified domain names. If your registrar requires using IP addresses, you can get the IP addresses for your name servers using the dig utility (for Mac, Unix, or Linux) or the nslookup utility (for Windows).

...and using the dig utility, only a single IP address is returned in the answer section, so using that is okay according to

share|improve this answer

You need to update the domain registrar settings for your DNS servers. The zone file you updated also needs to be done, but queries won't use Amazons servers until your registrar is updated. This updates the DNS root with a new place to resolve your domains; if that data was stored only in your zone file nobody would ever know where to get your zone data from in the first place.

Once you've changed your DNS values on the registrar it might take a day for everything to update.

share|improve this answer
That's how I'd normally do it, but the guide over at AWS suggests otherwise. have you read the AWS guide? – jkim Feb 12 '13 at 4:34

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.