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

January 19, 2018 10.2k views
DNS Configuration 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.

2 Answers

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

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.

  • One other thing to note.

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


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

    • 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?

      • 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.


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

        by Melissa Anderson
        A DigitalOcean Floating IP is a publicly-accessible static IP address that can be mapped to one of your Droplets. A Floating IP can also be instantly remapped, via the DigitalOcean Control Panel or API, to one of your other Droplets in the same datacenter. This instant remapping capability grants you the ability to design and create High Availability (HA) server infrastructures by adding redundancy to the entry point, or gateway, to your servers.
Have another answer? Share your knowledge.