Route 53 DNS_PROBE_FINISHED_NXDOMAIN using Netlify's DNS

I have a domain registered with AWS Route 53 and I’m trying to use Netlify DNS but I keep getting DNS_PROBE_FINISHED_NXDOMAIN even after waiting more than 24 hours.

I have tried setting my domain DNS to Netlify’s DNS and after it didn’t work I tried adding DNS and IP address

but I can’t seem to find the problem.
My netlify’s instance name is dreamy-mestorf-3c2bf6.netlify.com

Cheers and thank you!

Hi, @Jesusz0r. I’m showing this domain is currently configured to use Route 53, not Netlify DNS.

There are two commands/tools which I recommend for troubleshooting DNS issues: dig and whois.

First, there is the WHOIS data filtered for string “name server” (case-insensitive):

$ whois mendozajesus.com | grep -i "name server"
   Name Server: NS-1251.AWSDNS-28.ORG
   Name Server: NS-1873.AWSDNS-42.CO.UK
   Name Server: NS-632.AWSDNS-15.NET
   Name Server: NS-67.AWSDNS-08.COM
Name Server: ns-1251.awsdns-28.org
Name Server: ns-1873.awsdns-42.co.uk
Name Server: ns-632.awsdns-15.net
Name Server: ns-67.awsdns-08.com

This can be confirmed with dig also:

$ dig mendozajesus.com SOA +trace | tail -n 12
mendozajesus.com.	172800	IN	NS	ns-67.awsdns-08.com.
mendozajesus.com.	172800	IN	NS	ns-632.awsdns-15.net.
mendozajesus.com.	172800	IN	NS	ns-1251.awsdns-28.org.
mendozajesus.com.	172800	IN	NS	ns-1873.awsdns-42.co.uk.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A  NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20191217055123 20191210044123 12163 com. IFjYHBv2IJZ9OhwwsNw1ecOOkp7pleWQo8Cto/V2ya2VLktyjgKgGgcw XAUk9RTgyWOzjdzUGl3ApAwFJ6Cerma2Hlcukq0ec2n97IBlWwi9WqKU VZ1dkTYrriu/1JOnm1gpLFVs0JrlYQjfnSHKxbVIEv6DESAOcn8dNdLJ oKvALhpyjIQAjX0I8W3AeKpRTZVKHn45DkBi/V5znpUDwg==
BJ8JM0F3S4SOLBHON6P1VCKUNL51LVKD.com. 86400 IN NSEC3 1 1 0 - BJ8K7B695VA3LU4BTUEAL2D6935GA781  NS DS RRSIG
BJ8JM0F3S4SOLBHON6P1VCKUNL51LVKD.com. 86400 IN RRSIG NSEC3 8 2 86400 20191215063249 20191208052249 12163 com. RUP3POBAOBzlWTvJqwA7CapQ2zXbmXp5EopOQ+CkkY03USgjfU2pD/Oj 1iTI2vVmb8FhTYXN/Ka7WUi2XpkhgkbnmnaEVVO7c2TEXftVoB/vn/P5 Y7+EJPA5J4ybw9xxiJK7D2130JaDCJ8zGhJQ2c/JjCZ6H2Gx9DsFmvtD 2nAbVsiwNJCcYk/qyrFF/5+IOa7iez8bAuQzHNlnpzddQQ==
;; Received 746 bytes from 192.48.79.30#53(j.gtld-servers.net) in 56 ms

;; Received 34 bytes from 205.251.199.81#53(ns-1873.awsdns-42.co.uk) in 12 ms

Note, in the request above, I’m asking for the start of authority (SOA) record. The name servers are reported as AWS Route 53 name servers but, when dig queries one of those name servers, it doesn’t respond with an answer for the SOA record.

I believe the following instructions explain how to change a domain’s name servers are Route 53:

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#updating-name-servers-other-dns-service

Note, using Netlify DNS isn’t required to connect a domain name with a Netlify site (although it does automate certain features of our service, like SSL certificates for branch subdomains).

You can use AWS Route 53 for DNS and still connect the domain to Netlify using these instructions:

https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/

1 Like

Hey guys. I found the solution.

It turns out that you don’t have to change any record in your hosted zone. You need to go to:

Route 53 -> In the left Panel choose Registered Domains -> Select the domain you wish to change the DNS -> In the top menu choose Manage DNS -> Change all the records to Netlify DNS records.

Thanks for sharing how you solved it, @Jesusz0r.