none
nslookup DNS query - Request timed out couple of times and get the response(local dns zone) RRS feed

  • Question

  • Hi All,

    When I try to query for most of the record using nslookup, I get request timeout first time and get the response but once it is cached, I get the response immediately.

    The client/server is in same domain, querying the local dns zone where the client/server record resides.

    Screenshot attached for reference.

    Please let me know why the delay is?

    Thanks in advance,

    Srivari.

    >computer1.domain.com
    server:dc01.domain.com
    address:192.168.1.100

    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    Name: computer1.domain.com
    Address: 192.168.1.101


    Wednesday, October 2, 2019 9:40 AM

All replies

  • Hi ,

    Thanks for your posting in this forum.

    Did you create PTR records corresponding to these IP addresses in the Reverse Lookup Zones?

    If no, please create PTR records pointing to these IP addresses.

    If you have created PTR records and the phenomenon still happens, please turn on exhaustive debugging mode of NSlookup, this will display detailed information of name resolving process:

    >NSlookup
    >set d2
    >name of none cached machine

    Note: since this is a public forum, everyone could view your information, please remove private information that might leak your privacy.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   


    Thursday, October 3, 2019 6:27 AM
  • Hi ,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.                   

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Monday, October 7, 2019 5:21 AM
  • Hi ,

    If you have any updates during this process, please feel free to let me know.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Wednesday, October 9, 2019 6:21 AM
  • Hi ,

    Please put dot at the last of FQDN name and check if the issue still occurs.

    Without a trailing dot, you are asking your computer to try and guess the suffix added on to end of the name. It uses DNS search suffix.

    From the result you post, I find the other suffix:

    Here is a thread discussed before, you could have a look:

    Internal DNS nslookup error timeout was 2 second

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Wednesday, October 9, 2019 10:00 AM
  • Great!! Thanks a lot for your support!

    Wednesday, October 9, 2019 11:11 AM
  • Hi ,

    I’m pleased to know the information is helpful with you .

    You could mark the useful reply as answer if you want to end this thread up.

    If you have any concerns , please feel free to let me know.

    Best Regards,

    Candy

    Wednesday, October 9, 2019 1:14 PM
  • Hi ,

    Just checking in to see if the information provided was helpful. 

    Did you have any updates on this issue?

    Best Regards,

    Candy



    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Friday, October 11, 2019 2:11 AM
  • Yes. Thank you!
    Tuesday, October 22, 2019 6:00 PM
  • Hi ,

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Wednesday, October 23, 2019 1:26 AM