Doug walks you through
troubleshooting an unreachable website

route-53-dns-website-unreachable-doug

I've configured my website to use Amazon Route 53 for DNS services, but I can't access my website from the internet. How do I troubleshoot this issue?

Clients might be unable to access your website that uses Route 53 DNS services if:

  • The public hosted zone for your website's domain name isn't populated with the appropriate resource records sets.
  • The resource records sets in the website's public hosted zone aren't publicly accessible.
  • The domain name registrar for your website's domain name doesn't return the correct name server records (NS records).

Check the website's public hosted zone resource records sets

Be sure that the public hosted zone for your website's domain name in Route 53 contains the appropriate resource records sets. For more information, see Creating Records by Using the Amazon Route 53 Console and Editing Records. For record type-specific values, see Values That You Specify When You Create or Edit Amazon Route 53 Records.

Important: At a minimum, the public hosted zone must contain an address record (A record) for your domain.

Check if the resource records sets are publicly accessible

Make sure the resource record sets are publicly accessible from the internet. For more information, see How do I verify that resource record sets in an Amazon Route 53 public hosted zone are accessible from the Internet?

Check the domain name registrar's NS records

Check if your third-party domain name registrar returns the same four authoritative NS records as the domain's Route 53 public hosted zone.

Note: Skip this section if you use Route 53 as your domain name registrar.

  1. Note the four authoritative NS records for your domain in Route 53. For how to find these records, see Getting the Name Servers for a Public Hosted Zone.
  2. Query your preferred Whois utility (domain registration lookup tool) for your website's domain name.
  3. Check if the query returns the same NS records as your domain's Route 53 public hosted zone.
  4. If the NS records don't match, update the NS records for your domain name at the registrar to the four authoritative NS records in Route 53.

Note that Route 53 doesn't respond to DNS queries for a domain until the TTL (up to 48 hours) of the previous registrar's name servers expires at the TLD level. For more information, see Making Amazon Route 53 the DNS Service for an Existing Domain.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.

Published: 2015-09-30

Updated: 2018-10-12