none
Not stable DNS service RRS feed

  • Question

  • Hi all,

    we have a strange issue, when we run nslookup on local DNS 2012 server sometimes resolve its name and ip very nice, after 10 sec. if we rerun nslookup on the same server it returns "default server: unkown" with correct IP

    Note: DNS server has reverse lookup zone and all PTR records for DNS servers correctly configured    

    please help



    • Edited by Hany Lotfy Tuesday, April 26, 2016 1:20 PM
    Tuesday, April 26, 2016 7:20 AM

All replies

  • also when we run "dcdiag /test:dns", got 5 passes so there is no known issue
    • Edited by Hany Lotfy Tuesday, April 26, 2016 8:24 AM wrong synax
    Tuesday, April 26, 2016 7:21 AM
  • Hi Hany,

    Hi all,

    we have a strange issue, when we run nslookup on local DNS 2012 server sometimes resolve its name and ip very nice, after 10 sec. if we rerun nslookup on the same server it returns "default server: unkown" with correct IP

    Note: DNS server has reverse lookup zone and all PTR records for DNS servers correctly configured

    please help

    also when we run "dcdiag /test:dns", got 5 passes so there is no known issue

    Please disabled the ipv6 section on the NIC properties. Then using nslookup again to see if the issue still persists.

    Or, you could configure a related AAAA record for IPV6 on reverse lookup zone.

    Best regards,


    Andy_Pan

    Wednesday, April 27, 2016 7:22 AM
  • hi Andy, 

    thanks for reply, but ipv6 is already disabled on all domain controllers

    Wednesday, April 27, 2016 11:38 AM
  • Hello

    test with internal or external fqdn have same error?


    sorry my english

    Wednesday, April 27, 2016 5:14 PM
  • yes, with internal or external fqdn the same situation
    Wednesday, April 27, 2016 6:38 PM
  • Hello

    its new server or old?
    if old, the error is new? install patch or something?

    try: dnscmd /config /enableednsprobes 0


    sorry my english

    Wednesday, April 27, 2016 7:43 PM
  • it is new server, the old one was win 2003
    Thursday, April 28, 2016 5:50 AM
  • Hi Hany,

    Sorry for the late reply.

    Please also trying to using ipconfig /flushdns & dnscmd /clearcache commands to flush the dns caches on clients and server to see if it helps.

    Best regards,


    Andy_Pan

    Thursday, May 5, 2016 9:03 AM
  • thanks Andy for reply

    but i got some symptoms may lead to something,

    when run nslookup not always resolving the record but when adding "-retry=2" it always resolve perfectly on second retry

    please help

    Thursday, May 5, 2016 11:26 AM
  • Hi Hany,

    >>when run nslookup not always resolving the record but when adding "-retry=2" it always resolve perfectly on second retry

    Please check if your registry exists the following option:

    HKLM\System\CurrentControlSet\Services\dnscache\Parameters\DNSQueryTimeouts.

    For more related information, please refer to blog below:

    https://blogs.technet.microsoft.com/stdqry/2011/12/14/dns-clients-and-timeouts-part-2/

    Best regards,


    Andy_Pan


    • Edited by Hello_2018 Friday, May 6, 2016 2:20 AM
    Friday, May 6, 2016 2:20 AM
  • Hi Andy,

    I added this parameter but nothing changed.

    to more clarify the problem

    it is not an timeout issue because when run "nslookup -timeout=10 querytype=ns Zone_name 127.0.0.1" it can't resolve from first time

    but when run "nslookup -retry=2 querytype=ns zone_name 127.0.0.1" it always resolve correctly in second attempt.

    Sunday, May 8, 2016 6:37 AM
  • Hii All,

    when I monitored DNS performance counters I figured out that "recursive query timeout/sec" is about 50% of "recursive query/sec"

    Are there any known issue for this behavior  ???????

    Monday, May 16, 2016 5:20 AM