none
DNS request timed out

    Question

  • Hi All,

    We have strange DNS issue, I have installed new Win2008 R2 DC server in new forest /domain.

    This is the only DC/ Server in the Forest. DC Server has one nic and it has DNS server installed.

    When I run nslookup

    > abc.local
    Server:  DCServer.abc.local
    Address:  10.10.10.10    
    DNS request timed out.
    timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    Name:    DCServer.abc.local
    Addresses:  10.10.10.10

    >        

    Any idea why i get two DNS request timed out and finally i am able to reslove the name.



    • Edited by Ni0 Thursday, October 11, 2012 7:54 PM
    Thursday, October 11, 2012 4:06 PM

Answers

  • Hi All,

    We have strange DNS issue, I have installed new Win2008 R2 DC server in new forest /domain.

    This is the only DC/ Server in the Forest. DC Server has one nic and it has DNS server installed.

    When I run nslookup

    > abc.local
    Server:  DCServer.abc.local
    Address:  10.10.10.10    
    DNS request timed out.
    timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    Name:    DCServer.abc.local
    Addresses:  10.10.10.10

    >        

    Any idea why i get two DNS request timed out and finally i am able to reslove the name.


    Renukanath S

    If this is just a time out issue, and/or a CNAME TTL issue on certain public domain names, let's install these two hotfixes, test it, and get back to us:

    DNS Server service does not use root hints to resolve external names in Windows Server 2008 R2 - HOTFIX available.
    Article ID: 2616776 - Last Review: October 12, 2011, APPLIES TO •Windows 2008 R2 Datacenter •Windows 2008 R2 Ent •Windows 2008 R2 Std
    "Consider the following scenario:
    •You install the Domain Name System (DNS) Server role on a computer that is running Windows Server 2008 R2.
    •You configure the DNS server to use root hints to resolve external names.
    In this scenario, the DNS server does not use root hints to resolve external names and causes name resolution issues.
    This issue occurs because the DNS Server service in Windows Server 2008 R2 does not allow CNAME records and NS records to coexist. When the DNS Server service receives a response that has two kinds of records, it ignores the CNAME record.
    In lieu of installing the HOTFIX: "To work around the issue, configure the DNS server to use forwarders instead of root hints to resolve external names."
    (Takes care of time-out issues)
    http://support.microsoft.com/kb/2616776

    .

    DNS server stops responding to DNS queries from client computers in in Windows Server 2003, in Windows Server 2008 or in Windows Server 2008 R2
    "The DNS Server service on a DNS server that is running Windows Server 2003, Windows Server 2008 or Windows Server 2008 R2 intermittently does not respond to DNS queries from client computers. When this issue occurs, the DNS server stops responding."
    (Takes care of time-out issues)
    http://support.microsoft.com/kb/2655960

    .


    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Thursday, October 11, 2012 5:22 PM
  • It seems to me dns misconfig issue refer below link to ensure that DNS is set correctly on DC.
    Best practices for DNS client settings on DC and domain members.
    http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
    http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx

    It is not recommended from the MS to disable IPv6, take a look at below articles on IPv6.
    http://technet.microsoft.com/en-us/magazine/2009.07.cableguy.aspx

    Arguments against disabling IPv6
    http://blogs.technet.com/b/netro/archive/2010/11/24/arguments-against-disabling-ipv6.aspx

    IPV6 should be configured to dynamic (Automatically) as below.
     

    Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.If still the issue persist post the ipconfig /all details of DC and dcdiag /q output.

    Hope this helps


    Best Regards,

    Sandesh Dubey.

    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, October 13, 2012 1:57 PM

All replies

  • Hello,

    Please post unedited output of ipconfig /all > c:\ipconfig.txt command.

    As you have a single DC, please make sure that:

    • The DC has a single IP address in use
    • The DC is pointing to its private IP address as primary DNS server
    • The DC is pointing to 127.0.0.1 as secondary DNS server
    • Public DNS servers are set as forwarders and not in IP settings of DC

    Once done, run ipconfig /registerdns and restart netlogon on each DC you have.

    Any logged events in event viewer?


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Thursday, October 11, 2012 4:17 PM
  • Hi,

    Uncheck the Internet protocol (TCPIP/IPV6) setting in the Lan card setting.

    There is a specific forum for DNS related Threads. Please post this thread to the below forum.

    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/threads

    Regards

    Praveen


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, October 11, 2012 4:24 PM
  • Hi,

    Uncheck the Internet protocol (TCPIP/IPV6) setting in the Lan card setting.

    There is a specific forum for DNS related Threads. Please post this thread to the below forum.

    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/threads

    Regards

    Praveen


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Dear Praveen,

    This is not supported by Microsoft. I would highly recommend not disabling IPv6. If ::1 is set as a DNS server then it has to be removed and that is all.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Thursday, October 11, 2012 4:30 PM
  • Hi,

    Please read the Ace Fekay  post on the below post. It will help you to change the order from IPv6 to IPv4.

    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/a00525ab-c7c4-440a-8b45-01415bb1a0d8

    Regards

    Praveen


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, October 11, 2012 4:41 PM
  • Hi All,

    We have strange DNS issue, I have installed new Win2008 R2 DC server in new forest /domain.

    This is the only DC/ Server in the Forest. DC Server has one nic and it has DNS server installed.

    When I run nslookup

    > abc.local
    Server:  DCServer.abc.local
    Address:  10.10.10.10    
    DNS request timed out.
    timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    Name:    DCServer.abc.local
    Addresses:  10.10.10.10

    >        

    Any idea why i get two DNS request timed out and finally i am able to reslove the name.


    Renukanath S

    If this is just a time out issue, and/or a CNAME TTL issue on certain public domain names, let's install these two hotfixes, test it, and get back to us:

    DNS Server service does not use root hints to resolve external names in Windows Server 2008 R2 - HOTFIX available.
    Article ID: 2616776 - Last Review: October 12, 2011, APPLIES TO •Windows 2008 R2 Datacenter •Windows 2008 R2 Ent •Windows 2008 R2 Std
    "Consider the following scenario:
    •You install the Domain Name System (DNS) Server role on a computer that is running Windows Server 2008 R2.
    •You configure the DNS server to use root hints to resolve external names.
    In this scenario, the DNS server does not use root hints to resolve external names and causes name resolution issues.
    This issue occurs because the DNS Server service in Windows Server 2008 R2 does not allow CNAME records and NS records to coexist. When the DNS Server service receives a response that has two kinds of records, it ignores the CNAME record.
    In lieu of installing the HOTFIX: "To work around the issue, configure the DNS server to use forwarders instead of root hints to resolve external names."
    (Takes care of time-out issues)
    http://support.microsoft.com/kb/2616776

    .

    DNS server stops responding to DNS queries from client computers in in Windows Server 2003, in Windows Server 2008 or in Windows Server 2008 R2
    "The DNS Server service on a DNS server that is running Windows Server 2003, Windows Server 2008 or Windows Server 2008 R2 intermittently does not respond to DNS queries from client computers. When this issue occurs, the DNS server stops responding."
    (Takes care of time-out issues)
    http://support.microsoft.com/kb/2655960

    .


    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Thursday, October 11, 2012 5:22 PM
  • It seems to me dns misconfig issue refer below link to ensure that DNS is set correctly on DC.
    Best practices for DNS client settings on DC and domain members.
    http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
    http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx

    It is not recommended from the MS to disable IPv6, take a look at below articles on IPv6.
    http://technet.microsoft.com/en-us/magazine/2009.07.cableguy.aspx

    Arguments against disabling IPv6
    http://blogs.technet.com/b/netro/archive/2010/11/24/arguments-against-disabling-ipv6.aspx

    IPV6 should be configured to dynamic (Automatically) as below.
     

    Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.If still the issue persist post the ipconfig /all details of DC and dcdiag /q output.

    Hope this helps


    Best Regards,

    Sandesh Dubey.

    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, October 13, 2012 1:57 PM