Domain stuck at "Last step: Update your nameservers to activate Cloudflare"

Website, Application, Performance DNS & Network
1

What is the name of the domain?

daniqr.dk

What is the issue you’re encountering

Domain stuck at “Last step: Update your nameservers to activate Cloudflare”

What steps have you taken to resolve the issue?

I’ve tried deleting the Domain from Cloudflare and re-creating it.

I’ve tripled-checked that the Domain Name is the correct in Cloudflare

I’ve triple checked that the Name servers are correct on the Domain:

You can check here: Domain is not available | Punktum dk

I’ve checked with the Domain Registrar that DNS Sec is NOT activated on the Domain.

The Domain was registred with the Cloudflare DNS. I’ve tried updating the Domain with the (same) Cloudflare DNS information.

The problem has persisted for more than 17 hours since.

What feature, service or problem is this related to?

DNS not responding/updating

2

Seems the Name Server Names is changed by the Forum software. We’er using: blair and frank.

3

While your domain is showing Cloudflare nameservers in WHOIS, they are not showing at the .dk registry, which is returning nonexistent.punktum.dk for your domain. Contact your registrar to get this fixed.
https://cf.sjr.dev/tools/check?21166c8b037c48daa964339941851928#dns

2 Likes
4

According to our Registrar, everything is correct at their end:

I did check the .dk registry and the nameserver is correct as well

I asked them what Tools they used, and I got:

I checked two tools and only the one you have provided shows the error

The one I have = cf.sjr.dev :: Cloudflare Things

5

It’s not set at the registry, this is the test…

dig +trace +nodnssec daniqr.dk

; <<>> DiG 9.10.6 <<>> +trace +nodnssec daniqr.dk
;; global options: +cmd
.			86391	IN	NS	a.root-servers.net.
......
.			86391	IN	NS	m.root-servers.net.
;; Received 239 bytes from 127.0.2.2#53(127.0.2.2) in 0 ms

dk.			172800	IN	NS	b.nic.dk.
dk.			172800	IN	NS	c.nic.dk.
dk.			172800	IN	NS	h.nic.dk.
dk.			172800	IN	NS	l.nic.dk.
dk.			172800	IN	NS	s.nic.dk.
dk.			172800	IN	NS	t.nic.dk.
;; Received 402 bytes from 2001:503:c27::2:30#53(j.root-servers.net) in 26 ms

daniqr.dk.		300	IN	NS	nonexistent.punktum.dk.
couldn't get address for 'nonexistent.punktum.dk': not found
dig: couldn't get address for 'nonexistent.punktum.dk': no more

dig daniqr.dk @b.nic.dk

; <<>> DiG 9.10.6 <<>> daniqr.dk @b.nic.dk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24455
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;daniqr.dk.			IN	A

;; AUTHORITY SECTION:
daniqr.dk.		300	IN	NS	nonexistent.punktum.dk.

;; Query time: 44 msec
;; SERVER: 2a01:630:0:80::53#53(2a01:630:0:80::53)
;; WHEN: Thu Jan 16 10:57:33 GMT 2025
;; MSG SIZE  rcvd: 72
3 Likes
6

The .dk registry has their own special system where you might need to change the nameservers yourself directly with the registry instead of relying on your registrar to do so. Might be that’s your problem:

1 Like
7

I found the Solution, but for others with the same issue:

Turns out the Danish TLD had send us a mail where we were asked to confirm the registration. Once that was completed, everything started working.

Thanks for all your help!

1 Like
8

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