Question

Unable to verify domain through Google Search Console

Hello, I’m trying to do the above via https://search.google.com/search-console/welcome?utm_source=about-page, however every time I’m getting the folowing error: “Could not find your domain. Confirm that you provided the correct domain for your property.”.

I have added various verification TXT entries multiple times and waited enough for propagation, but no luck.

The domain is accessible trough a browser. If howevever you do dig -t txt happybeeclothes.co.uk, the response is SERVFAIL:

 dig -t txt happybeeclothes.co.uk

; <<>> DiG 9.11.3-1ubuntu1.16-Ubuntu <<>> -t txt happybeeclothes.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 45288
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;happybeeclothes.co.uk.         IN      TXT

;; Query time: 266 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Jan 01 20:08:45 UTC 2022
;; MSG SIZE  rcvd: 50

Two things to note though:

  • when I purchased the domain, I couldn’t add it to my Droplet. I had to ask DO to help me verify that I’m the (current) owner of the domain,
  • domain has been purchased through Namecheap, but again you can access the website hosted on my Droplet.

What am I doing wrong?


Edit: DO own tool also doesn’t find any TXT records on my domain, even though I have now 3 of them: https://www.digitalocean.com/community/tools/dns?domain=happybeeclothes.co.uk


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

Solved! The issue was with one of the TXT keys. Because it was malformed, none of the others were accessible.

Interesting.

Have you added the ns1 to ns3 DNS for digitalocean to your Namecheap? If not, please do.

From checking with DNS nodes, it doesn’t appear there’s any propagation happening for the TXT at all anywhere in the world (https://dnschecker.org/#TXT/happybeeclothes.co.uk)