Nameserver's update pending

I’m trying to configure the domain esponsor.gg, already updated the nameservers in the domain provider (which does not implements DNSSEC)

This domain was previously configured by me but I lost it for a month and then repurchased, so it was deleted from cloudflare and now I’m trying to reconfigure it and is not working

[corrected]
Although you have set nameservers at the registrar, it seems they are not yet reflected from the .gg root servers. Check with your registrar…
https://cf.sjr.org.uk/tools/check?9db7740e5dd64fe78584fc1910a94b57#whois

1 Like

Thanks for the replay, I checked with them and they sent me this Home :: Channel Isles: The Islands' Domain Names

For some reason it appears right there but wrong in the url you just send

As I said, they show correctly in the WHOIS, but they are not in the DNS. The registry isn’t delegating the nameservers to those.

dig +trace +nodnssec esponsor.gg ns

; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> +trace +nodnssec esponsor.gg ns
;; global options: +cmd
.			4117	IN	NS	k.root-servers.net.
.			4117	IN	NS	d.root-servers.net.
.			4117	IN	NS	i.root-servers.net.
.			4117	IN	NS	a.root-servers.net.
.			4117	IN	NS	h.root-servers.net.
.			4117	IN	NS	e.root-servers.net.
.			4117	IN	NS	m.root-servers.net.
.			4117	IN	NS	j.root-servers.net.
.			4117	IN	NS	c.root-servers.net.
.			4117	IN	NS	b.root-servers.net.
.			4117	IN	NS	f.root-servers.net.
.			4117	IN	NS	l.root-servers.net.
.			4117	IN	NS	g.root-servers.net.
;; Received 239 bytes from 127.0.0.53#53(127.0.0.53) in 0 ms

gg.			172800	IN	NS	c.ci-servers.org.
gg.			172800	IN	NS	e.ci-servers.net.
gg.			172800	IN	NS	dns1.nominetdns.uk.
gg.			172800	IN	NS	dns2.nominetdns.uk.
gg.			172800	IN	NS	dns3.nominetdns.uk.
gg.			172800	IN	NS	dns4.nominetdns.uk.
;; Received 453 bytes from 193.0.14.129#53(k.root-servers.net) in 12 ms

gg.			86400	IN	SOA	c.ci-servers.org. dnsmaster.channelisles.net. 2024041102 21600 3600 2592000 86400
;; Received 146 bytes from 2001:500:14:6074:ad::1#53(e.ci-servers.net) in 0 ms

It is likely due to the “Locked by Registry” in the status.

You need to push the registrar to fix it.

1 Like

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