Site cannot be reached after delegating the domain to Netlify DNS

[sahil97]

Hello everyone,
I’m facing some trouble delegating my custom domain to use the netlify DNS for a static site. The site works on the netlify domain which is listed below but does not work with the custom domain.

Netlify app: https://isamundo-prod.netlify.app/
Custom Domain: isamundo.org, getting DNS_PROBE_FINISHED_NXDOMAIN.

I’ve waited for more than 24 hours, tried reseting my broswer’s cache, resetting my OS cache, tried it on my mobile network but still the site cannot be reached and I am getting the above error on the webpage.

Here are the logs from the dig and whois commands on the troubleshooting guide.

➜  ~ dig isamundo.org NS +trace | tail -n 6   
isamundo.org.		3600	IN	NS	dns1.p09.nsone.net.
isamundo.org.		3600	IN	NS	dns2.p09.nsone.net.
isamundo.org.		3600	IN	NS	dns3.p09.nsone.net.
isamundo.org.		3600	IN	NS	dns4.p09.nsone.net.
;; Received 130 bytes from 198.51.44.9#53(dns1.p09.nsone.net) in 25 ms

➜  ~ whois isamundo.org | grep -i "name server"                   
Name Server: dns1.p09.nsone.net
Name Server: dns2.p09.nsone.net
Name Server: dns3.p09.nsone.net
Name Server: dns4.p09.nsone.net
Name Server: dns3.p09.nsone.net
Name Server: dns4.p09.nsone.net
Name Server: dns1.p09.nsone.net
Name Server: dns2.p09.nsone.net

From the above logs, it looks like the DNS delegation was successful. What am I missing ? and what other troubleshooting steps I can take to resolve this?

I appreciate the help. Thank you.

[dig]

Have you assigned isamundo.org to a production site yet @sahil97?

Further reading

[Support Guide] Compiled resources for production domains on Netlify and DNS settings -- start here!

Hi there! We know that using your own production domain (Example: http://somecooldomain.com) on a Netlify site can be a bit confusing at times. The good news is that our team has written an abundance of guides covering various questions regarding domains. This listing has all of our “best practice” guides about configuring and using Netlify DNS and production domains on our service, grouped by topic area. We have a few guides that cover multiple topic areas, so we have listed them under …

[sahil97]

Yes, I did add that to the production site. Seems like I just had to wait. It started working last night.
The redirection works now, but shows as not secured and that the cerificate is not valid.
On the ‘Domain Management’ page it still shows as 'Awaiting External DNS` in front of the external domain and thus I cannot add the SSL/TLS certificate. It has been more than 48 hours as of now.

[dig]

I only see AAAA (IPv6) records for isamundo.org and no A (IPv4)

Assuming you have NETLIFY and NETLIFYv6 type records for isamundo.org then everything is correct.

In either case, I’ll have to leave this in the hands of Netlify support.

[sahil97]

Thank you for taking the time to look into this.
Is there a way to add the A records ?
I deleted all the DNS records from the custom domain provider(I moved the mail records first to netlify) and the external domain now only has name servers pointing to netlify.
Is there any other steps I should/can take ?

[dig]

You could try the DIY options from @luke in the following post as I believe your issue is the same.

Robots.txt and stuck on awaiting external dns

Hi, @ElevationSpot. I’ve made a change and NETLIFY and NETLIFYv6 type DNS record, which were not working, are working now. If this happens again and you do not want to wait for our support team to make the fix, this is how you can self-serve a fix without waiting for us to do so: delete any NETLIFY and NETLIFYv6 records which are not working from the DNS settings page in the screenshot remove the domain from the site’s domain management settings add the domain back in the place it was just de…

[luke]

Hi, @sahil97. Or you can wait for me to make the fix.

It should be working now but if not, please let us know.

[sahil97]

Awesome. The site is working now with the SSL updated.
Thank you @luke and @dig for the help.