Domain moved status for days

My registrar made a mistake over the weekend and did not automatically renew my domain. The domain was then renewed manually and works again (nameservers were corrected again), but in the Cloudflare Dashboard the domain is still shown as “moved”. Domain changes don’t seem to go through either, only the pre-incident entries seem to work.
When I open the overview of the domain, it remains blank. Under DNS → “Cloudflare nameservers” I also have no way to trigger a manual recheck. I have also tried several devices and web browsers.
How can this be fixed? The nameserver change was made more than 48h ago.

Glad to hear any hints :slight_smile:
Xedon

Can you share your domain, so it is easier for us to debug?

the domain is “x20.cc”

The nameservers that I see are DANE.NS.CLOUDFLARE.COM and GRACE.NS.CLOUDFLARE.COM. Is that what they are supposed to be, correct? If I remember correctly there should be a banner that sets something like SETUP here which should have a link to manually retrigger the verification.

the nameservers are correct. As I said the button is not there. For me this looks like a bug.
It is still not working :frowning:

No, it’s not a bug. The ns changed, the zone shows as moved, that is all visible in your dash

Screenshot 2023-02-15 at 9.26.06 AM

Select

Screenshot 2023-02-15 at 9.27.17 AM

yes but the nameserver was wrong maybe one hour. It was corrected again immediately. Since then, the overview of the domain remains empty and under DNS I can not request a recheck.
The DNS change is now 4 days ago.

please select

Screenshot 2023-02-15 at 9.27.17 AM

when i do this it just comes “page already exists”.

Can you attach a screen shot of that error?

I have to post this one by one, because I’m a new member^^

this is how the overview of the domain looks like.
(There should be data)

here should be a button for a recheck

the domain cannot be recreated because it already exists

in the total overview it looks like this
grafik

Hello Xedon, you won’t get to request a recheck from your dashboard when the domain status is Moved. That function is while the domain is being onboarded while Pending.

Our developer documents cover domain statuses (except pending) here - Domain statuses · Cloudflare DNS docs

When I do a dig on the zone’s nameservers I get the query status REFUSED:

dig ns x20.cc       

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 1937.     <---- Refused Status
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;x20.cc.				IN	NS.                 <---- No nameservers returned

This shows the issue is with your registrar, and I’d contact for further troubleshooting.

In addition, a zone with a moved status can get deleted from the account if in that state too long (7 days). I’d record any setting you have just in case it does get removed. Here is how you can download the DNS records, the rest you’ll have to record manually - Import and export records · Cloudflare DNS docs

1 Like

Okay, now it’s getting really interesting.
I did the same with a few more servers and got a different result.
First my local dns:

dig ns x20.cc
; <<>> DiG 9.16.33-Debian <<>> ns x20.cc
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11593
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;x20.cc.                                IN      NS

;; ANSWER SECTION:
x20.cc.                 86400   IN      NS      dane.ns.cloudflare.com.
x20.cc.                 86400   IN      NS      grace.ns.cloudflare.com.
;; Query time: 23 msec
;; SERVER: 10.1.1.4#53(10.1.1.4)
;; WHEN: Wed Feb 15 20:20:59 CET 2023
;; MSG SIZE  rcvd: 91

Google:

dig ns x20.cc @8.8.8.8
; <<>> DiG 9.16.33-Debian <<>> ns x20.cc @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34314
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;x20.cc.                                IN      NS

;; ANSWER SECTION:
x20.cc.                 21600   IN      NS      dane.ns.cloudflare.com.
x20.cc.                 21600   IN      NS      grace.ns.cloudflare.com.

;; Query time: 15 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Feb 15 20:24:39 CET 2023
;; MSG SIZE  rcvd: 91

Cloudflare:

dig ns x20.cc @1.1.1.1
; <<>> DiG 9.16.33-Debian <<>> ns x20.cc @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37071
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;x20.cc.                                IN      NS

;; ANSWER SECTION:
x20.cc.                 86400   IN      NS      dane.ns.cloudflare.com.
x20.cc.                 86400   IN      NS      grace.ns.cloudflare.com.

;; Query time: 11 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Feb 15 20:26:12 CET 2023
;; MSG SIZE  rcvd: 91

The test with this website is also successfull DNS Checker - DNS Check Propagation Tool

1 Like

Nice! Not sure what happened, but it looks good now. When I checked DNS Checker for propagation earlier it was full of red Xs.

Checking dig again, I’m not getting the REFUSE error and Cloudflare’s nameservers show.

dig ns x20.cc      

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8610        <------
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 7

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;x20.cc.				IN	NS

;; ANSWER SECTION:
x20.cc.			86400	IN	NS	dane.ns.cloudflare.com.
x20.cc.			86400	IN	NS	grace.ns.cloudflare.com.

Once the nameservers have propagated globally, and Cloudflare does another check, the domain should change to active.

1 Like

yes it looks like this for me for days (even on Saturday half an hour after the incident).
with the page linked above you can also see well whether the DNS changes have already arrived worldwide. After 4 days, the change should really have arrived at every point on the planet.
Something else is not right, I just suspect that a small error has crept into the system. Maybe you can start a manual recheck?

can someone please help me with this problem?
The status is still moved and tomorrow the zone will probably be deleted (7 days)… Somewhere a bug has occurred. Someone probably would only have to manually press “recheck” :frowning:

@Xedon Could you run this API call:

curl --location --request PATCH 'https://api.cloudflare.com/client/v4/zones/[zoneID]' \
--header 'X-Auth-Email: EMAIL \
--header 'X-Auth-Key: APIKEY' \
--header 'Content-Type: application/json' \
--data-raw '{
    "status":"pending"
}'
2 Likes