Receiving queryNs ESERVFAIL Error after providing service account key
-
Trying to setup and test out Cloudron. I followed the instructions here https://cloud.google.com/dns/docs/quickstart to move my domain hosted on Google Domains to Google Cloud DNS. I created a service account key in JSON format and tried to upload and received queryNs ESERVFAIL. Any suggestions on what may have gone wrong? What I should check? I will also add that I performed the clean-up steps at the end of the instructions provided here https://cloud.google.com/dns/docs/quickstart#clean-up. Which had me deleting the A record and CNAME record and zone previously setup. I'm not a devops person, so I may have missed something obvious. Thanks for any help.
-
@derek Switching name servers usually takes around 2-4 hours depending on the provider. You can test this on the cloudron (and on your PC/Mac):
host -t NS example.comIf the above works on Cloudron, then it will start working. When a transfer is going on, it will give out
ESERVFAIL.
-
Thank you. It's failing for now, so I will give it more time.
-
@girish said in Receiving queryNs ESERVFAIL Error after providing service account key:
Switching name servers usually takes around 2-4 hours depending on the provider.
In rare cases, this can take up to 24-48 hours (I've seen this happen as well).
-
I'm still getting the same error. Can someone confirm whether or not following the clean up steps here https://cloud.google.com/dns/docs/quickstart#clean-up could be causing a problem? I didn't understand why you would setup an A and CNAME and then delete them and the zone? Thanks!
-
I think I missed this step after creating the CNAME it says "The record update takes some time to propagate depending on the time-to-live (TTL) values of the records. You can verify that the DNS records are working by visiting the domain name and confirming that the domain resolves to your IP address."
I assume I needed to wait for for the domain to resolve to the IP before doing the clean-up? Can anyone confirm? Thanks!
-
Hi @derek sorry for the delayed answer, did you manage to solve this after the TTLs have expired from your attempts?
