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

We recently moved our web application to AWS. One thing that is still managed by our old hoster is DNS.

OLD HOSTER    NS     <Old hoster's name server>    A      <ElasticIP on EC2 instance>

I'm now trying to setup and play around with Route53 and use it for name resolution of our EC2 instances.


Now my question: Is it possible to forward DNS queries for * to Route53 ( What kind of record would I have to add?


Now I've got the following NS records:

OLD HOSTER: Zone      NS     <Old hoster's name server>      A      <ElasticIP on EC2 instance>
*    CNAME


ROUTE53: Zone         NS         NS         NS         NS  CNAME  CNAME

However, when I'm doing a nslookup for I get the A record (ElasticIP) from the old server. When I do a lookup for the host on I do get the CNAME record. So the problem is somewhere with the old DNS service I'd guess.

Do I need to add something to the zone (not the zone) on AWS?

TTLs are at 3600, so that should not be the problem.

Many thanks for any additional help.


This is my final setup.

OLD HOSTER: Zone      NS     <Old hoster's name server>  NS  NS  NS  NS      A      <ElasticIP on EC2 instance>
*    CNAME

ROUTE53: Zone         NS         NS         NS         NS  CNAME  CNAME
share|improve this question
up vote 4 down vote accepted

You would add appropriate NS records for pointing to Route53's name servers. For example: IN NS IN NS IN NS
share|improve this answer
David's answer is correct. But to clarify, you need to add NS records on both the old DNS server (to get DNS transferred to Route 53) and on Route 53 itself (to keep it pointed there after the transfer). Route 53 will provide these three NS hosts for you when you create the entry there. It will take time for this migration to take effect, depending on your timeout settings at your old DNS provider. – platforms Nov 15 '12 at 12:54
Yes, quite correct. The zone on your server needs these entries. And Route 53 needs an zone that also contains these NS entries as well as whatever else you want it to do. – David Schwartz Nov 15 '12 at 13:07
Hi! I've updated the question and any additional help would be appreciated. Thx. :) – Philippe Gerber Nov 16 '12 at 13:43
Make sure there's no zone on the old server. – David Schwartz Nov 16 '12 at 21:15

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.