Nameserver errors (Cloudflare or GoDaddy)

I had my Cloudflare tunnel working on my domain virtualvault dot us for a month, and accidently changed nameservers in bulk at Uniregistry.

Then I got migrated to GoDaddy (they acquired Uniregistry). I realized the error and 4 days ago changed nameservers on GD, but the site will not resolve to Cloudflare. I’ve read there are some possible issues with Afternic/GD now but they are slow to realize something is up.

I’m getting very strange Dig returns (gobbledegook) and certain NS check tools find no nameservers set at all.

For example dnschecker reports errors, but GD whois shows the correct CF servers set.

Can anyone give me something to provide to GoDaddy; very hard to even open a ticket with them these days, Tier 1 was brutal.

I’m curious if you are having the same issue as I.

I had my Cloudflare tunnel working and accidently changed nameservers, then got migrated to GoDaddy (they acquired Uniregistry). I realized the error and 4 days ago changed nameservers on GD, but the site will not resolve to Cloudflare. I’ve read there are some possible issues with Afternic/GD now but they are slow to realize something is up.

I’m getting very strange Dig returns and certain NS check tools find no nameservers set.

dnschecker reports errors but GD whois shows the correct CF servers set.

It looks like your site isn’t active on Cloudflare. Nameservers are showing Cloudflare, but they aren’t responding.

dig virtualvault.us @1.1.1.1 +short
 dig +trace virtualvault.us

; <<>> DiG 9.18.12-0ubuntu0.22.04.1-Ubuntu <<>> +trace virtualvault.us
;; global options: +cmd
.                       84335   IN      NS      j.root-servers.net.
.                       84335   IN      NS      e.root-servers.net.
.                       84335   IN      NS      d.root-servers.net.
.                       84335   IN      NS      i.root-servers.net.
.                       84335   IN      NS      h.root-servers.net.
.                       84335   IN      NS      f.root-servers.net.
.                       84335   IN      NS      a.root-servers.net.
.                       84335   IN      NS      k.root-servers.net.
.                       84335   IN      NS      l.root-servers.net.
.                       84335   IN      NS      m.root-servers.net.
.                       84335   IN      NS      c.root-servers.net.
.                       84335   IN      NS      b.root-servers.net.
.                       84335   IN      NS      g.root-servers.net.
;; Received 239 bytes from 127.0.0.53#53(127.0.0.53) in 0 ms

us.                     172800  IN      NS      b.cctld.us.
us.                     172800  IN      NS      f.cctld.us.
us.                     172800  IN      NS      k.cctld.us.
us.                     172800  IN      NS      w.cctld.us.
us.                     172800  IN      NS      x.cctld.us.
us.                     172800  IN      NS      y.cctld.us.
us.                     86400   IN      DS      46144 8 2 0C67E6017124BF19D50BE565CC486FF3CFE2A278FE2E5983FF97B2A4 53386419
...

virtualvault.us.        3600    IN      NS      kia.ns.cloudflare.com.
virtualvault.us.        3600    IN      NS      zeus.ns.cloudflare.com.
...
;; Received 645 bytes from 37.209.194.15#53(x.cctld.us) in 32 ms

;; Received 50 bytes from 108.162.193.249#53(zeus.ns.cloudflare.com) in 16 ms
dig SOA virtualvault.us @1.1.1.1

; <<>> DiG 9.18.12-0ubuntu0.22.04.1-Ubuntu <<>> SOA virtualvault.us @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 41329
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation virtualvault.us.)
; EDE: 23 (Network Error): ([2606:4700:58::adf5:3bf9]:53 rcode=REFUSED for virtualvault.us SOA)
;; QUESTION SECTION:
;virtualvault.us.               IN      SOA

;; Query time: 20 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Wed May 31 09:34:58 CEST 2023
;; MSG SIZE  rcvd: 152

I’m not sure if I can open a ticket with Cloudflare as an unpaid user.

Wow, not obvious that the domain was totally yanked from Cloudflare. All my configs were there and Tunnel healthy.

Seems like room for improvement on GUI of cloudflare.

Thanks @Laudian

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