It seems the domain hasn't been verified yet on cloudflare yet https://whois.domaintools.com/ekspresbetalinger.dk shows the correct cloudflare nameservers.
#DK domain is behaving oddly
gleaming garden
One thing I have noticed is that the whois info is very concise, unlike other TLDs i've used before. Cloudflare usually verifies my .CZ domains within about 5 minutes of me registering and changing dns. On this DK domain, the changing of nameservers was done pretty quickly, I checked on https://punktum.dk after about 10 minutes, it was changed. However, on whois.domaintools.com it took about a day to update.
steady elm
It seems the domain hasn't been verified yet on cloudflare yet https://whois.dom...
I would guess related to this: https://www.cloudflarestatus.com/incidents/vp0dwbjll8zf
gleaming garden
It's been 3 days since the domain was registered, after many rechecks, no luck
gleaming garden
I would guess related to this: https://www.cloudflarestatus.com/incidents/vp0dwb...
Potentially, however that issue has impacted me elsewhere (verifying via txt records on google search console, took about 30 minutes as opposed to the usual 30 seconds)
steady elm
oh I see opps, jumped the gun on that. They are set right in whois, but the ns servers for dk don't return them
gleaming garden
This issue was reported 28 minutes ago, I've had this nameserver issue for the past 3 days
steady elm
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;ekspresbetalinger.dk. IN NS;; AUTHORITY SECTION:
ekspresbetalinger.dk. 300 IN NS nonexistent.punktum.dk.
gleaming garden
yeah no worries
gleaming garden
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SE...
Where did you find this?
steady elm
I just queried the nameservers for dk
gleaming garden
That's from punktum.dk
steady elm
dig ns dk
;; QUESTION SECTION:
;dk. IN NS
;; ANSWER SECTION:
dk. 86400 IN NS a.nic.dk.
dk. 86400 IN NS b.nic.dk.
dk. 86400 IN NS c.nic.dk.
dk. 86400 IN NS d.nic.dk.
dk. 86400 IN NS l.nic.dk.
dk. 86400 IN NS s.nic.dk.
dig ns ekspresbetalinger.dk @a.nic.dk
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> ns ekspresbetalinger.dk @a.nic.dk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23036
;; 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:
;ekspresbetalinger.dk. IN NS
;; AUTHORITY SECTION:
ekspresbetalinger.dk. 300 IN NS nonexistent.punktum.dk.
;; Query time: 116 msec
;; SERVER: 2001:1580:0:180d::122#53(a.nic.dk) (UDP)
;; WHEN: Thu Nov 30 16:11:38 GMT 2023
;; MSG SIZE rcvd: 83
I checked a few, they all seem to think the domain doesn't exist
gleaming garden
I've contacted the registry and hopefully they'll get back to me
steady elm
The whois status shows
Status: Reserved
which may be of interest
gleaming garden
That might be it
steady elm
Thank you for registering your .DK domain name with us. Your registration is on hold as the .DK registry requires that the Registrant (Domain owner) validates the registration.
The .DK registry asks that .DK domain names are activated within 25 days of receipt of the email confirming their reservation. Following activation, the registry will assign the name to you. If the domain is not activated within 30 days of receiving the email from the registry, the domain will be deleted by the registry.
To activate your domain name, please find your user ID and PIN code in the confirmation email sent by the .DK registry. We ask that you log into your DK-Hostmaster account or sent us the login and password via the contact form from your account so that we can activated for you.
We urge you to respond promptly; regrettably, if you fail to respond within the given time, the .DK registry will cancel the reservation without warning and the domain name will become available to everyone.
It's a bit weird though as usually when an action like this is taken the domain doesn't resolve at all, but ccTLDs have a bit more freedom and that seems to be the cause
inner edge
@gleaming garden i use this to check NS propagation: https://www.whatsmydns.net/#NS/ekspresbetalinger.dk
steady elm
<@516317697617690628> i use this to check NS propagation: https://www.whatsmydns...
If you're debugging a ns issue I would query the tld ns rather then use that, those are recursive resolvers so you can end up with issues like the user didn't change the nameservers at their registrar, but instead at their dns host, and that would "look" correct
inner edge
If you're debugging a ns issue I would query the tld ns rather then use that, th...
that makes sense, its more of a "sanity check" to see if the issue is upstream
steady elm
For sure, it still has it uses. For DNSSEC issues as well, if you're using a tool like that, you'd see a few ISP Resolvers who don't check DNSSEC work and may falsely think its a propagation issue. If you dig a resolver like 1.1.1.1 or 8.8.8.8 that supports extended dns errors it would show you the error instantly. In dig we trust lol
lapis forge
That might be it
Just to confirm -
It is the reserved state that makes the problem here, because you haven't yet activated your new domain.
Exact same issue as over here:
-> https://community.cloudflare.com/t/is-nameserver-check-broken/581782/7
lapis forge
Awww crap, I need a danish ID to verify
Danish ID should only be mandatory, if you actually appear to be from Denmark.