Related

Tool Instant DNS Lookup Tool Tool
"Domain Name Already Exists" Error - When Adding DNS for Droplet Question Question
How to setup domain masking for external domains? Question Question

Question

Unable to verify domain using DNS TXT record after adding it.

Posted January 19, 2018 36.5k views
DNSConfiguration Management

i wanted to verify my newly added domain ..by adding nameserver to move it from godaddy to digital ocean and have made it live.However i wanted to verify my domain name by using TXT to my domain as suggested by google webmaster. - https://www.google.com/webmasters/verification/home?hl=en

 Add the TXT record below to the DNS configuration for mywebsite.com.

I successfully created a new TXT record under Networking and added it with my domain name.So in the DNS records table, i can see new entry as shown below - 

Type    Hostname           Value                                                                  TTL (seconds) 
 TXT         MYDOMAIN         pasted the value provided by google                      3600

But after trying to verify my domain..it fails always.Wondering where i went wrong.
Kindly help.

Add a comment
Milind1011
By:
Milind1011

Related

Tool Instant DNS Lookup Tool Tool
"Domain Name Already Exists" Error - When Adding DNS for Droplet Question Question
How to setup domain masking for external domains? Question Question

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.

×
4 answers
zachgoll October 10, 2019

I was having this problem (Oct, 2019), and here was my solution:

Problem: I was setting the text record on the full domain. For example, I was adding the prefix “www” in the TXT record, which assigned the text record to my full domain - www.thediygolfer.com.

Solution: In the “hostname” section of Digital Ocean networking, you need to put the “@” symbol, which will assign the text record to the top level domain (i.e. “thediygolfer.com”) rather than the subdomain (i.e. “www.thediygolfer.com”).

Hope that helps someone!

Reply Report
  • colston February 7, 2021

    and any luck with google domains like mine Shayri.page which is not pointing to https status . more than 72 hours passed

    This site can’t be reached Check if there is a typo in www.Shayri.page
    If spelling is correct,
    try running Windows Network Diagnostics.
    DNSPROBEFINISHED_NXDOMAIN

    any help . please

    Reply Report
jasonjpeters January 20, 2018

How long did you wait?
You may need to wait up to 12 - 48 hours for propagation

Reply Report
Milind1011 January 20, 2018

its almost close to 24 hrs but i wlll wait more one day to get this into effect.Thanks for the highlighting this.
I knew this but i forgot as changes in DNS take some time.Will update after two days.Thanks for your time.

Reply Report
  • jasonjpeters January 26, 2018

    One other thing to note.

    Have you updated the DNS of your domain name to the digitalocean nameserver(s):

    ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

    This will be required for DNS to work under the Digitalocean networking section.

    Reply Report
    • Milind1011 January 27, 2018

      i already have the same setting but its not working.

      DNS records

Type                    Hostname                       value
A                            www.mydomain.com          directs to 139.**.**.**   

TXT                          www.mydomain.com         returns google-site-verification=MKtQS_Ympu4gUpmqU2xxxxxxxxxxxxxxxx
NS                           www.mydomain.com          directs to ns3.digitalocean.com

NS                            www.mydomain.com          directs to ns1.digitalocean.com

NS                           www.mydomain.com         directs to ns2.digitalocean.com

      What is wrong here?

      Reply Report
      • jasonjpeters January 28, 2018

        OK

        Where you registered your domain (GoDaddy, namecheap, etc…) you need to ensure that your domain has the name servers set to ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com. You may need to consult your registrar on how to set this, but usually it is pretty straight forward. Take note that if a change is needed it will take some time to propagate.

        Once that is complete - In your Digitalocean Control Panel navigate to the networking area and select the domain you would like to work with.

        The basic entries for your DNS should be as follows…

        Type: A -- Hostname: DOMAINNAME.TLD -- Value: XXX.XXX.XXX.XXX
Type: CNAME -- Hostname: www.DOMAINNAME.TLD -- Value: DOMAINNAME.TLD
Type: NS -- Hostname: DOMAINNAME.TLD -- Value: ns1.digitalocean.com
Type: NS -- Hostname: DOMAINNAME.TLD -- Value: ns2.digitalocean.com
Type: NS -- Hostname: DOMAINNAME.TLD -- Value: ns3.digitalocean.com

        Replace DOMAINAME.TLD with your domain name and XXX.XXX.XXX.XXX with the IP/Floating IP of your droplet.

        If you’re not using a Floating IP I would suggest to do so. Here is a great tutorial regarding that.

        https://www.digitalocean.com/community/tutorials/how-to-use-floating-ips-on-digitalocean

        When this is complete your domain using either mydomain.com or www.mydomain.com will resolve to the droplet IP/Floating IP

        Reply Report
charlesb6347cdbb293659d75d August 25, 2019

Hi,
I have the same problem. I am trying to assign this personal URL
https://sites.google.com/s/10Q2zChTVUJ-Ro1FvAofS26AmHSaG4GJ6/p/1Dicn6c0QLV2aylDPkkmvg5nXTWtGWIGF/edit?pli=1&authuser=1

to www.wingsoverafrica.org

This is a domain that I own through Godaddy. I have added the TXT record, and the CNAME record and the A record also exists.

I have attached the screenshot of the DNS record at Godaddy. The CNAME record verifies, but the TXT record refuses to verify, so I am unable to add my custom URL. It would appear that instead of using either TXT record or a CNAME record, Google looks for a TXT record first, and if that fails to verify, it doesn’t bother with the CNAME record. This looks like sloppy programming to me.

What exactly is the issue here? I will just say that this is an extraordinarily complicated verification process, and I think Google could simplify and streamline this

Thanks

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help