When you are using the dig command, what DNS servers are you querying?
It sounds like there may be a name server (NS) mismatch between the domain registrar and your hosted zone.
Please try the following:
- Get the name servers for a public hosted zone.
- Search for your website's domain name using your preferred WHOIS utility (domain registration lookup tool).
- Verify if the NS for your domain in the WHOIS output matches the same NS records in your Route 53 public hosted zone.
- If the NS records don't match and your domain registrar is Route 53, then update the name servers for your domain at the registrar to the four authoritative NS records assigned to your Route 53 public hosted zone. Note: For domains registered with third-party registrars, follow your registrar's documentation to change the domain's NS.
Note: It might take until the TTL (up to 48 hours) for the previous registrar's NS to expire from the top-level domain (TLD). During this period, DNS queries for the domain might be sent to both Route 53 and the prior registrar's NS. Route 53 immediately responds to DNS queries for the domain from resolvers that haven't cached the prior registrar's NS.
I hope this information is helpful.
Can I use Route 53 with an .ai domain name?asked 6 years ago
Route 53 Registered Domain Not ResolvingAccepted Answerasked 3 years ago
How can I get the IP address of my domain.?asked a month ago
DOMAIN NAME NOT REFLECTING HOSTED ON ROUTE 53asked a month ago
How to add PTR DNS record for my EIP without AWS-hosted Forward zone?Accepted Answerasked 3 months ago
How can I resolve Route 53 dns after ICANN suspended the domain name?asked 3 months ago
Route 53 showing IP in browser instead of my domain nameasked 2 years ago
Add a custom domain to AWS Amplify react-appasked 2 years ago
Why doesn't my hosted zone A record resolve correctly for an .io domain?Accepted Answerasked 3 days ago
Getting DNS_PROBE_FINISHED_NXDOMAIN Connected Route 53 to Google Domainasked a year ago