External dns txt records are not processed RRS feed

  • Question

  • I am using windows server 2008 r2

    ran into the problem that the command “nslookup –type = txt” does not return the answer for some domains where this record actually exists. I have an nslookup running if I search for mx-record, a-record, etc., but txt-record doesn't work. Tell me what could be the problem? Below I attach an example of the executed commands:

    Windows PowerShell
    Copyright (C) 2016 Microsoft Corporation. All rights reserved.

    PS C: \ Users \ Administrator> nslookup -type = mx

    Non-authoritative answer: MX preference = 10, mail exchanger =
    PS C: \ Users \ Administrator> nslookup -type = a

    DNS request timed out.
        timeout was 2 seconds.
    Non-authoritative answer:

    PS C: \ Users \ Administrator> nslookup -type = txt

    *** can't find Unspecified error
    PS C: \ Users \ Administrator>
    Thursday, February 11, 2021 9:27 AM

All replies

  • Hi there, I had a similar issue a while ago, just to ask? Are you using a CDN like Cloudflare, if so which one? If you are using Cloudflare I simply contacted them via email and they got back to me the next day and had fixed it, not sure about other CDN's like Amazon ect but if your using Cloudflare they should be able to help you out, not sure what they did but they emailed me the next day saying that they had resolved the issue hope this helps :)
    Friday, February 12, 2021 11:05 AM
  • That's typical for nslookup and is not an issue.
    If you do this manually you should get a result like so:
    Default Server:  GJKLDJLK

    > set type=txt
    Server:  GJKLDJLK

    Non-authoritative answer:       text =

            "have-i-been-pwned-verification=13c7b50cd0b12f85dabe796e6178fb74"       text =

            "2e35680fa5ac784cf58deca180385b5eff74dfeb831c2d73830425e8a8deb7d5"       text =

            "df22d6d27ce9cb078b94c5edcf1d6d2d78a24e1ef8b488427eca5d0ee675129a"       text =

            "mailru-verification: 530c425b1458283e"       text =

            "v=spf1"       text =

            "MS=ms75457885"       text =

            "ebc00251b60542877fd641b73ad533da27c74a98b4b4164b6152bf44bc457d42"       text =

            "_globalsign-domain-verification=lD5-OgV_QE93G8rzNaeJKvtqe9tlP5AZtyDodrldYh"       text =

            "facebook-domain-verification=e750ewnqm68u4f83wvp6qp7iiphkj0"       text =


    I think nslookup doesn't like TCP and with big answers like this DNS responds with TCP and not the default UDP protocol.
    Should be somewhere in

    • Edited by Jevez Friday, February 19, 2021 10:36 AM
    • Proposed as answer by Steve Mighty Wednesday, March 17, 2021 7:15 PM
    Friday, February 19, 2021 10:33 AM
  • This is the command I have successfully run in my console


    Default Server:  mydnsserver

    > set type=txt


    Server:  mydnsserver


    *** No text (TXT) records available for


    Tuesday, March 23, 2021 10:06 AM
  • I have a similar problem, thanks for the answers!
    Tuesday, March 23, 2021 4:47 PM
  • Web browsers tend to blame any connectivity issues on DNS issues. For example, a physical router plug failure is not a “DNS issue,” but your browser might tell you it is. If a user is complaining about a DNS issue, you may want to go through basic troubleshooting for them first. It could solve many problems before you spend time on a more in-depth network investigation.

    Check your cables and connections: If you have wired connections, make sure everything is plugged in properly. If you are on a wireless network, make sure your Wi-Fi is on and you are connected. Make sure your router is plugged in and functional.
    Reboot your router: Wait a minute before turning it back on again and wait until the indicator lights stop blinking before trying to connect.
    Run a malware scan: In some cases, a virus may be blocking internet access. In this case, you may have bigger issues to deal with before you address IP connectivity.
    Check the site: If you are having trouble accessing a particular website (your own or someone else’s), confirm that the problem is with DNS and not the site itself. One way to do this is with a website like DownForEveryoneOrJustMe. Similarly, you can issue the ping command for your web address with the command prompt. If it responds, it means the site is live and you just can’t access it, which suggests that the problem is indeed with your DNS. If the result of the ping is that “request could not find host,” it suggests the website is down, which is not necessarily a DNS problem.


    Rachel Gomez

    Friday, August 19, 2022 5:00 AM
  • Thanks for posting in Q&A platform.

    Please try first start nslookup without parameters, then type set type=txt, then type the domain name.

    Friday, August 19, 2022 9:54 PM
  • Add a TXT record Sign in to your domain's account at your domain host. Locate the page for updating your domain's DNS records. Locate the TXT records for your domain on this page. Add a TXT record for the domain and for each subdomain (see "Use Cases" below). Regards, Peter
    Saturday, August 20, 2022 4:51 AM