Cloudflare shows 'invalid nameservers' but they're properly configured at registrar

What is the name of the domain?

satovsky social

What is the error message?

invalid nameservers

What is the issue you’re encountering

The nameservers are set properly at my registrar (Hover), but Cloudflare does not see the configured nameservers. The domain name was transferred from Google (as registrar) immediately before switching the nameservers/DNS to Cloudflare. Both NSlookup & whois using Google’s servers fails (as if they didn’t completely release the domain - Hover confirmed it’s configured properly on their end…), but NSLookup & whois works fine non-google servers / services and the domain generally works (even though Cloudflare reports the nameservers are incorrect).

What steps have you taken to resolve the issue?

Removed and re-added the nameservers at the registrar (reversing the order); Re-added the domain to Cloudflare; Contacted my registrar - they could only confirm everything is setup correctly on their end, but cannot contact Google.

What feature, service or problem is this related to?

Nameservers

What are the steps to reproduce the issue?

Running nslookup satovsky.social on most servers works, but running it on Google: nslookup satovsky.social 8.8.8.8 (or 8.8.4.4) fails. Whois works at most registrars, but fails on Google’s whois servers.

You have DNSSEC turned on at your domain registrar. Please turn it off, and then you can re-configure it once you get DNS up and running at Cloudflare.

More details here:
https://cf.sjr.dev/tools/check?9dc1e7ec465f4f7aab60057294fd8a62

Thank you, that is odd, my registrar simply shows DNSSEC is not supported for .social domains. I will need to contact them…

1 Like

I see it on two lists for DNSSEC:

1 Like

Thank you, turning off DNSSEC at my registrar resolved the issue.

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.