'nslookup' can not find new TXT record comes from MS Azure!

  • Posted September 23, 2021
  • DNS

Hello, I’m facing with an issue related to the new TXT record that I’ve added but the nslookup query can not resolve the request.

MS Azure service has provided a TXT record/value to be added (1) and I’ve added it to the DO side (2). The thing is I can not validate this new record on the MS Azure side because it can not resolve/reach to it. I’ve gone manually to ensure DO has the TXT record with nslookup but it also says the 'server can’t find … '.

Here is the sample query:

nslookup -type=TXT
Server:		127.XX.XX.XX
Address:	127.XX.XX.XXX#XX

** server can't find NXDOMAIN

Am I adding the record correctly, is there any missing setup? I’ve already tried setting the TXT record name as and underscore version that it shows on the screenshot;

Thanks for your help.

(1) Here is the domain details from Azure side @ (2) And the screenshot from DO side @


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

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.


There is no need to add the DNS records in the two zones. The record needs to be added to the active DNS zone, for example, if your domain name is using the DigitalOcean nameservers, then it means that you need to add the TXT record under your DigitalOcean DNS zone.

Also, note that once you add a new DNS record it could take up to 24 hours for the DNS to propagate over the Globe before you could see the changes.

You can use this tool here to do the DNS lookups:

Hope that this helps. Regards, Bobby