DK domain is behaving oddly
It seems the domain hasn't been verified yet on cloudflare yet https://whois.domaintools.com/ekspresbetalinger.dk shows the correct cloudflare nameservers.
23 Replies
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.
I would guess related to this: https://www.cloudflarestatus.com/incidents/vp0dwbjll8zf
It's been 3 days since the domain was registered, after many rechecks, no luck
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)
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
This issue was reported 28 minutes ago, I've had this nameserver issue for the past 3 days
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;ekspresbetalinger.dk. IN NS ;; AUTHORITY SECTION: ekspresbetalinger.dk. 300 IN NS nonexistent.punktum.dk.
yeah no worries
Where did you find this?
I just queried the nameservers for dk
That's from punktum.dk
I checked a few, they all seem to think the domain doesn't exist
I've contacted the registry and hopefully they'll get back to me
The whois status shows
Status: Reservedwhich may be of interest
That might be it
https://help.eurodns.com/s/article/my-dk-domain-is-in-reserved-status?language=en_US
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
@Martin i use this to check NS propagation: https://www.whatsmydns.net/#NS/ekspresbetalinger.dk
DNS Propagation Checker - Global DNS Checker Tool
Instant DNS Propagation Check. Global DNS Propagation Checker - Check DNS records around the world.
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
that makes sense, its more of a "sanity check" to see if the issue is upstream
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
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
Awww crap, I need a danish ID to verify
This'll be interesting
Danish ID should only be mandatory, if you actually appear to be from Denmark.
Well the registrar I used say that there is a way to do it with foreign ID, via customer support, so we shall see