Troubleshooting Amazon Route 53
This page covers the following troubleshooting topics for Amazon Route 53:
Domain unavailability:
Understand common reasons why your domain might be unavailable on the internet, such as not confirming the registrant email, DNS service transfer issues, incorrect name server settings, or deleted hosted zones.
Domain suspension:
Learn about the causes of domain suspension (ClientHold status) and how to get your domain unsuspended, including expired domains, unverified registrant email changes, and payment processing issues.
Failed domain transfer:
Discover common reasons for a failed domain transfer to Route 53, such as not authorizing the transfer, invalid authorization codes, or issues with internationalized domain names.
DNS settings not taking effect:
Troubleshoot situations where your DNS settings changes haven't taken effect yet, including DNS resolver caching, incorrect name server updates, and multiple hosted zones with the same name.
"Server Not Found" error:
Find solutions for "Server Not Found" errors in your browser, such as missing records, incorrect record values, or unavailable resources.
Routing traffic to S3 buckets:
Resolve issues when trying to route traffic to an Amazon S3 bucket configured for website hosting.
Billing issues:
Understand common billing scenarios, including being billed twice for the same hosted zone, multiple invoices for domains, and domain registration concerns when your AWS account is closed or permanently closed.
Topics
- My domain is unavailable on the internet
- My domain is suspended (status is ClientHold)
- Transferring my domain to Amazon Route 53 failed
- I changed DNS settings, but they haven't taken effect
- My browser displays a "Server not found" error
- I can't route traffic to an Amazon S3 bucket that's configured for website hosting
- I was billed twice for the same hosted zone
- I was charged multiple invoices for my domain
- My AWS account is closed or permanently closed, and my domain is registered with Route 53