Domain – Nameserver is not authoritative for the domain

dns-zonedomaindomain-name-systemgoogle-cloud-dnsnameserver

It's more than 48h ago, since I've updated the nameservers of my domain "blocky.host" to Google Cloud DNS.

However my domain is not propargating as seen here
If I check my domain on diverse web-tools, I get these errors:

Nameserver ns-cloud-b1.googledomains.com/2001:4860:4802:32::6b did not return NS records. RCODE was REFUSED

Nameserver is not authoritative for blocky.host

This is my GCP console:

What can I do about it?

Best Answer

I was able to fix it by deleting that zone and creating a new one. Google Cloud assigned me new nameservers, which are working now!

Related Solutions

Moving a Registered Authoritative Nameserver to Another Server

Assuming the domain in question corresponds to example.com, and that ns and ns2 are under that domain, you will also need to update the records for those entries with your domain registrar.

For example:

your domain is awesome.local
you have NS records that point to ns.awesome.local and ns2.awesome.local
you have A records for ns and ns2 that point to 172.27.100.10 and 172.27.100.20 (substituting your values for my arbitrary examples)

You will need to:

update the A records for ns and ns2 to your new IP addresses
update the IP address listed with your registrar to the new IP addresses (this procedure varies between registrars, but it most commonly under some kind of advanced settings section)

It's also common to lower the TTL of the records in advance so that the old records will time out from cache faster. After the migration is complete. bump them back up to your regular values. This is optional, and can sometimes help speed up the process of propagating the new records.

Domain is reporting incorrect Name Server information

Focusing on the actual problem with your domains:

Following the chain of delegations for lamardesigngroup.com you'll see a delegation to ns1.lamardesigngroup.com and ns2.lamardesigngroup.com with glue referring to 212.1.213.8.

lamardesigngroup.com.   172800  IN      NS      ns1.lamardesigngroup.com.
lamardesigngroup.com.   172800  IN      NS      ns2.lamardesigngroup.com.
ns1.lamardesigngroup.com. 172800 IN     A       212.1.213.8
ns2.lamardesigngroup.com. 172800 IN     A       212.1.213.8

However, the authoritative records served by 212.1.213.8 are:

lamardesigngroup.com.   86400   IN      NS      ns2.lamardesigngroup.com.
lamardesigngroup.com.   86400   IN      NS      ns1.lamardesigngroup.com.
ns1.lamardesigngroup.com. 14400 IN      A       198.20.251.113
ns2.lamardesigngroup.com. 14400 IN      A       198.20.251.114

There's clearly an inconsistency between the glue and authoritative address records for the nameserver names, leading to different addresses being used in different situations.

This in turn also affects your other domains that use ns1.lamardesigngroup.com and ns2.lamardesigngroup.com as nameservers.

Best Answer

Related Solutions

Moving a Registered Authoritative Nameserver to Another Server

Domain is reporting incorrect Name Server information

Related Topic