Another "website not active (DNS modification pending)" question

Website, Application, Performance DNS & Network
1

I’ve read my way through the posts about this issue and still no result. Nameservers for the domain xvr.cloud look good in my opinion. Does anyone have any pointers in what could be wrong here? The DNS setting have not been changed in over a week and rechecking in the Cloudflare account is without result.

Thanks in advance!

2

This WHOIS lookup still shows name servers at counterpointhosting

3 
$ dig +short NS xvr.cloud @1.1.1.1
kurt.ns.Cloudflare.com.
dina.ns.Cloudflare.com.
$ whois xvr.cloud
Name Server: ns1.counterpointhosting.nl
Name Server: ns2.counterpointhosting.nl

You should contact your registrar (antagus.de) about this.

4

Lost in te world of DNS translation. I always assumed the WHOIS was pointing at the name of the registrar and thus the nameservers were correct. According to: DNS Propagation Checker - Global DNS Testing Tool the nameservers have been set correctly.

Thanks for your help! I will contact my registrar about this.

5

To start off with, remember that WHOIS is informational and has no technical relevance to how requests to your domain are handled. Tools such as dig can help you learn the truth, and luckily there are some free web tools which make dig accessible.

Currently xvr.cloud is not pointing to Cloudflare and we can see here.

However, by adding +trace we can see what is going on: the .cloud servers tell us that for xvr.cloud we should ask ns1.counterpointhosting.nl:

xvr.cloud. 3600 IN NS ns1.counterpointhosting.nl.
xvr.cloud. 3600 IN NS ns2.counterpointhosting.nl.
;; Received 85 bytes from 37.209.194.10#53(37.209.194.10) in 16 ms

Then when you ask ns1.counterpointhosting.nl, it says try asking kurt.ns.Cloudflare.com:

xvr.cloud. 3600 IN NS kurt.ns.Cloudflare.com.
xvr.cloud. 3600 IN NS dina.ns.Cloudflare.com.
;; Received 170 bytes from 185.194.251.170#53(185.194.251.170) in 98 ms

However, this is a horizontal delegation which is not permitted in DNS. You must go to the registrar where the domain was registered and update the nameserver delegation records there. What you have actually done is changed the records at the host (these look similar, but have a different technical result).

2 Likes
6

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