AWS dns_probe_finished_nxdomain - aws dns out of sync for external host

Question

Hello,
For some time now, a "dns_probe_finished_nxdomain" type error has magically appeared when it worked fine before. After several days I was able to temporarily fix the problem by passing my DNS settings from the external host I use instead of the AWS DNS. However I would like to reuse AWS DNS as before.

To give some information, I have an EC2 instance with different S3 services...
I had put parameters in the DNS Route 53 towards a subdomain. But the host was not AWS but another host in which there are the DNS settings of my domain name.
When the error appeared my DNS for the domain name was working fine, the problem came from my subdomains and therefore from the AWS DNS.

If you have any suggestions for me that could help me explain why it suddenly crashed and fixed it, thank you :)

Answer

Hello, here are some possible solutions you can try for troubleshooting :)

- **Determine if the domain status: Active or Suspended (clientHold)**

1. Install *whois*
For the instruction how to install *whois*: https://www.cyberciti.biz/faq/how-to-install-whois-on-ubuntu-debian-linux/

2. Run the following command to check the domain status
**For Window**s: Open a Windows command prompt, and then enter **whois -v example.com.**
**For Linux**: Open your **SSH client.** In the command prompt, enter **whois example.com.**

**- Make sure that the your domain name is on the domain register**

1. In the *whois* output, note the Name Servers
2. Open the Route 53 console
3. Confirm that the Name Servers listed in the Host zone details are the same to the Name Servers in 1.

**- Check for subdomain delegation issues**

1. Check the parent hosted zone (**example.com**) for a Name Server record for the domain name: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-listing.html
2. Confirm that the parent hosted zone contains a record for the (sub)domain name that you're trying to resolve
3. For more information on configuring multiple levels of subdomain delegation, see https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html#dns-routing-traffic-for-sub-subdomains

**- Check if the issue you encounter is the result of negative caching**

1. Note that **NXDOMAIN** response is considered a negative response, being stored in negative caching from an authoritative name server in the cache
2. Note that **NXDOMAIN** response usually occurs when the record **neg.example.com** doesn't exist

AWS dns_probe_finished_nxdomain - aws dns out of sync for external host

Relevant content