Note that there are some explanatory texts on larger screens.

plurals
  1. POAWS Route 53 DNS propagation time
    text
    copied!<p>About 5 hours ago I have created a new Hosted Zone in AWS Route 53 service. The records look like as follows:</p> <p><strong>Hosted Zone domain.com</strong></p> <pre><code>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 </code></pre> <p>I have also updated domain records for my registrar to specify AWS DNS servers there.</p> <p>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.</p> <p>The official AWS documentation says:</p> <blockquote> <p>Question: How quickly will changes I make to my DNS settings on Amazon Route 53 propagate globally?</p> <p>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).</p> </blockquote> <p>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: </p> <pre><code>nslookup domain.com 8.8.8.8: can't find domain.com: NXDOMAIN </code></pre> <p>Could you say if I performed DNS setup wrong so that DNS records have not been propagated yet?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload