0

I followed the steps in the tutorial: https://cloud.google.com/dns/docs/tutorials/create-domain-tutorial

However when I get to the verify my setup, I don't see my servers IP, instead I see this:

$ dig -t NS dandyrobot.com.

; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> -t NS dandyrobot.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56042
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 2339 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Tue Feb 07 11:00:42 EST 2023
;; MSG SIZE  rcvd: 43

Are there any additional steps I can take to narrow down what the problem is?

brad
  • 930
  • 9
  • 22
  • Did you register your domain under Google Domains? – Yvan G. Feb 07 '23 at 17:11
  • Yes, and added the custom name servers there as well – brad Feb 07 '23 at 17:28
  • The information you shared shows that your domain is dandyrobot.com right? Can you type the external IP address of your website to the address bar to check if it is working. Also consider the [propagation](https://cloud.google.com/dns/docs/update-name-servers#:~:text=can%20take%20from-,48%20to%2072%20hours,-to%20propagate.) that may take 48 to 72 hours – Yvan G. Feb 07 '23 at 17:40
  • Yeah thats correct. I can confirm it is working using the external IP. I went through the tutorial on Friday, so should be long past the 72 hours – brad Feb 07 '23 at 17:53
  • Can you share the NS server from your Cloud DNS? – Yvan G. Feb 07 '23 at 17:56
  • ns-cloud-d1.googledomains.com ns-cloud-d2.googledomains.com ns-cloud-d3.googledomains.com ns-cloud-d4.googledomains.com – brad Feb 07 '23 at 18:02
  • I tried to dig the domain and it is showing a different name server NS-CLOUD-A1.GOOGLEDOMAINS.COM NS-CLOUD-A2.GOOGLEDOMAINS.COM NS-CLOUD-A3.GOOGLEDOMAINS.COM NS-CLOUD-A4.GOOGLEDOMAINS.COM can you double check the configuration of your google domain and make sure that custom name server is in use. You can use this [link](https://support.google.com/domains/answer/3290309?hl=en) for guidance. – Yvan G. Feb 07 '23 at 18:11
  • Ah you are right, I was looking at the wrong google domain page. Should be correct now, but will give it more time to fully propagate before verifying – brad Feb 07 '23 at 18:30
  • Nice, that is great to hear. Please keep us users posted on this concern. Once the changes are already propagated Ill post our solution as an answer to guide other users with the same concern. – Yvan G. Feb 07 '23 at 19:14
  • Based on a `nslookup` command, it looks like its getting the right IP address! – brad Feb 08 '23 at 13:58

1 Answers1

1

Based on our conversation what seems to be the problem is that the configuration of custom nameserver under Google Domains. Then we use this link as a guidance to resolve this concern.

Yvan G.
  • 753
  • 1
  • 8