AWS Route 53 DNS propagation time

dns amazon-route53
Maksim picture Maksim · Mar 2, 2013 · Viewed 18.8k times · Source

About 5 hours ago I have created a new Hosted Zone in AWS Route 53 service. The records look like as follows:

Hosted Zone domain.com

domain.com.     A
domain.com.     MX   1 ASPMX.L.GOOGLE.COM.
                     5 ALT1.ASPMX.L.GOOGLE.COM.
                     5 ALT2.ASPMX.L.GOOGLE.COM.
                     10 ASPMX2.GOOGLEMAIL.COM.
                     10 ASPMX3.GOOGLEMAIL.COM.
domain.com.     NS   ns-1042.awsdns-02.org.
                     ns-996.awsdns-60.net.
                     ns-280.awsdns-35.com.
                     ns-1711.awsdns-21.co.uk.
domain.com.     SOA  ns-1042.awsdns-02.org.
                     awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
www.domain.com. A    XX.XXX.XX.XXX

I have also updated domain records for my registrar to specify AWS DNS servers there.

The record A for domain.com. is empty because it is just an alias for www.domain.com. subdomain from the same Hosted Zone. So www.domain.com. referes to a real Elastic IP address.

The official AWS documentation says:

Question: How quickly will changes I make to my DNS settings on Amazon Route 53 propagate globally?

Amazon Route 53 is designed to propagate updates you make to your DNS records to its world-wide network of authoritative DNS servers within 60 seconds under normal conditions. Note that caching DNS resolvers are outside the control of the Amazon Route 53 service and will cache your resource record sets according to their time to live (TTL).

In my case DNS records have not been propagated yet after 5 hours. I see that AWS DNS servers have already updated the records. So nslookup shows Elastic IP address for my web service properly for ASW DNS servers. But, for example, google DNS still does not know it: 

nslookup domain.com 8.8.8.8: can't find domain.com: NXDOMAIN

Could you say if I performed DNS setup wrong so that DNS records have not been propagated yet?

Answer

Joel Colucci picture Joel Colucci · Oct 19, 2016

I ran into a similar issue. The Registar NS records for the domain need to be updated to match the NS records within the hosted zone.

See the following for answer for instructions and thorough description: https://stackoverflow.com/a/37534217/3895401

Related questions

Set up DNS based URL forwarding in Amazon Route53

I'm trying to setup forwarding in Amazon Route53. My last DNS service (Nettica) allowed me to route requests to "aws.example.com" to "https://myaccount.signin.aws.amazon.com/console/". Is this functionality supported by Route53? How does Nettica achieve …

Read More
RRSet of type CNAME with DNS name foo.com. is not permitted at apex in zone bar.com

I own foo.com and bar.com. I am managing both in Route53. foo.com hosts my site, and I'd like to direct traffic from bar.com to foo.com. I tried to set up a CNAME record for bar.…

Read More
Exporting DNS zonefile from Amazon Route 53

I would like to export a DNS zonefile from my Amazon Route 53 setup. Is this possible, or can zonefiles only be created manually? (e.g. through http://www.zonefile.org/?lang=en)

Read More