Doug walks you through
troubleshooting an unreachable website

route-53-dns-website-unreachable-doug

I am using the Route 53 DNS service but am unable to access my website.

If the public hosted zone that you configure for the Amazon Route 53 DNS service is not populated with the appropriate resource record sets or if your website's domain name registrar does not reference the same name server records defined in the name server (NS) resource record set of the Route 53 public hosted zone for your website, clients will be unable to access your website.

  1. Review Values that You Specify When You Create or Edit Amazon Route 53 Resource Record Sets to ensure that you have created the appropriate resource record sets in the public hosted zone for your website. At a minimum, the public hosted zone must contain an address (A) record for your website.
  2. If you are using a domain name registrar other than Route 53, verify that your domain name registrar is referencing the same name server records as those defined in the NS resource record set of the Route 53 public hosted zone for your website. Note that the name server record must be the original record assigned when you create the hosted zone. To do this, query an Internet-based whois utility such as the InterNIC Whois Search web page to do the following:
    • Determine the domain name server records specified by your website’s domain name registrar - Enter the domain name of your website in the query field, select the Domain option, and then choose Submit. For example, if your website name is www.example.com, enter the domain name example.com in the query field. The query results should return the four authoritative name server records designated by the current domain name registrar for the specified domain.
      Note
      If the domain name registrar name server records do not correlate to the NS resource record set of the Route 53 public hosted zone for your website, DNS queries for your website will not be sent to this Route 53 public hosted zone. In this case you must ask the domain name registrar to update the domain name server records to match the name server records defined in the NS resource record set of the Route 53 public hosted zone.
    • If you are in the process of switching to another registrar for your website's domain name, verify that the current registrar for your website's domain name does not delete the domain name server records before the name server record time to live (TTL) period expires. This can take 48 hours or more, and Route 53 DNS services will not respond to DNS queries for a domain name until the TTL period for the domain name server records has elapsed. For more information, see Waiting for Your Changes to Take Effect.
  3. Ensure that clients can access resource record sets in the Route 53 public hosted zone for your website. 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?

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.