Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Google Cloud DNS Serving Very Old DNS Info

My domain Web3cryptos.com is serving up Wix DNS info. I haven't hosted with them in years. Setting up the zone and nameserver only seems to do a partial propagation and it's serving up a big Wix ad on my domain. This of course is extremely frustrating as I left Wix 2 years ago. This all started when I decided to leave Cloudflare and stop using my regstrar's DNS (which is Cloudflare too) All my other domains are resolving or propagating, even some that also had the Wix dns settings, but not this domain.

I have talked to Wix and they suggested my registrar give a NIC bump to the registry. I have talked to my registrar. My registrar insists I must have settings in my zone file. I do not. I even deleted and recreated the file/record. Here is what his dig results are saying:  If anyone can tell me what's going on, how it happened and how to fix it, I would be very grateful. 

Thank you,
Edmund

dig ns @ns-cloud-c1.googledomains.com web3cryptos.com

; <<>> DiG 9.10.6 <<>> ns @ns-cloud-c1.googledomains.com web3cryptos.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45150
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;web3cryptos.com.		IN	NS

;; ANSWER SECTION:
web3cryptos.com.	86400	IN	NS	ns13.wixdns.net.
web3cryptos.com.	86400	IN	NS	ns12.wixdns.net.

;; Query time: 57 msec
;; SERVER: 216.239.32.108#53(216.239.32.108)
;; WHEN: Thu Feb 01 18:07:47 PST 2024
;; MSG SIZE  rcvd: 92

 

1 2 263
2 REPLIES 2

Update. I switched over to Amazon Route 53, hoping this resolves matters, but if anyone more knowledgable of DNS wishes to offer a reason why this would happen, I would love to know.

Hi @Brego ,

I also use a digtool (result), and I am seeing NS records, which I believe is AWS. You can click the dig result that I shared on the link. 

To resolve the issue, you need to update the NS records for your domain to point to the correct DNS servers, which are likely the AWS DNS servers.