Nameserver verification is not working

[mawx]

I transferred my long-standing domain to my Cloudflare account. I have numerous domains that I’ve successfully transferred to Cloudflare over the years, so I’m accustomed to this process. I’ve set the nameservers at my registrar, but Cloudflare is showing that the nameservers have not been set.

When I use nslookup in a command prompt, it shows the correct nameservers (Cloudflare) and correct DNS. However, when I switch the server to 1.1.1.1 and do the same, it shows the wrong nameservers.

The Cloudflare portal sometimes shows an error “API Request Failed.”

I have screenshots. Below is a copy/paste of my nslookup commands:

C:\Windows\system32>nslookup
Default Server:  UnKnown
Address:  10.2.0.1

> server 8.8.8.8
Default Server:  dns.google
Address:  8.8.8.8

> set type=ns
> williamsonclan.us
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
williamsonclan.us       nameserver = aaron.ns.cloudflare.com
williamsonclan.us       nameserver = crystal.ns.cloudflare.com
> set type=mx
> williamsonclan.us
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
williamsonclan.us       MX preference = 1, mail exchanger = aspmx.l.google.com
williamsonclan.us       MX preference = 10, mail exchanger = alt3.aspmx.l.google.com
williamsonclan.us       MX preference = 10, mail exchanger = alt4.aspmx.l.google.com
williamsonclan.us       MX preference = 5, mail exchanger = alt1.aspmx.l.google.com
williamsonclan.us       MX preference = 5, mail exchanger = alt2.aspmx.l.google.com
> server 1.1.1.1
Default Server:  one.one.one.one
Address:  1.1.1.1

> set type=ns
> williamsonclan.us
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
williamsonclan.us       nameserver = ns1.hover.com
williamsonclan.us       nameserver = ns2.hover.com
>

[sandro]

You seemingly changed your nameservers only half an hour ago. 1.1.1.1 actually has the correct nameservers in most places already, but it may still be somewhere cached.

Nameserver changes can generally take up to two days. Your domain is generally correctly configured.

[mawx]

I’m not concerned about what 1.1.1.1 says or what is cached. I’m concerned about the errors on the Cloudflare page and not being able to set up the domain. I keep trying to post a screenshot, but my images are being rejected. Trying once more.

[sandro]

Well, your entire posting was about nameservers. So what is the issue? You can ignore the browser warnings, these are intermittent errors. And yes, your domain is enabled on Cloudflare.

[mawx]

My post heading was “Nameserver verification is not working” and I was referring to the Cloudflare nameserver verification process and the Cloudflare website. Due to the errors, the lack of lookup, and the fact that it appeared successful on most DNS resolvers, but the Cloudflare site was not agreeing with standard tools. Yes, I know it’s enabled, it’s the fact that my dashboard is not showing that it’s enabled that is the problem. I can’t currently manage my domain on Cloudflare, despite it clearly being verified, because the Nameserver process appears broken on the Cloudflare site.

Also, 1.1.1.1 is a DNS Resolver, not a Nameserver

Further, the error I’m receiving does not appear to be a “warning” but an actual error by the virtue of the use of the word “Failed” and the use of the color red.

Here’s what I see on my Cloudflare console (if the forum will let me post):

[sandro]

@mawx

Also, 1.1.1.1 is a DNS Resolver, not a Nameserver

Are you trying to lecture me here? I am not sure if this is appropriate when asking for help.

Anyhow, if you say you are familiar with Cloudflare’s system you will know that a nameserver verification is not instant, but can take a few hours. Your domain is currently correctly configured and will validate the next time when Cloudflare checks.