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