Question
"Failed to validate nameserver records: a non DigitalOcean Name Server was found for [domainname].com domain
- Posted on October 6, 2023
- Let's EncryptSecurity
Asked by e5f1a562a340477681cc68b8038ed1
Hi, I have my domain with Google domain. I am using the www and admin subdomains to point to my digitalocean droplet, but I have other sub domains pointing to AWS services.
When I try to generate a Letsencrypt certificate, I get this error: “Failed to validate nameserver records: a non DigitalOcean Name Server was found for [mydomain].com domain.”
Is it because of the other subdomains pointing to AWS? When creating the domain in DigitalOcean, I only specified the subdomains that are pointing to Digitalocean. Still I get this error.
Any idea how I can fix this without having to remove AWS services?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Heya,
If you’ve made a recent DNS change this can be related to the DNS propagation time as it usually takes several hours for the DNS to update due to DNS cache and general DNS propagation time.
You can use our DNS lookup tool to ensure that the DNS records are all set correctly:
https://www.digitalocean.com/community/tools/dns
Regards
Heya,
The error you’re encountering suggests that at least one of the nameservers for
example.comisn’t set to DigitalOcean’s nameservers.If you were to use the following DNS lookup tool, do you get the correct NameServers back:
Also, just to confirm, you’ve added your main domain name as a domain name to your DigitalOcean account and also updated your NameServers to the DigitalOcean ones correct?
ns1.digitalocean.comns2.digitalocean.comns3.digitalocean.com