none
Name resolution for the name <domain name> timed out after none of the configured DNS servers responded.

    Question

  • Hello,

    I have a machine running Server 2008 R2 with Active Directory. However I recently noticed that I get a warning from DNS Client Events every 10 minutes or so with the message:

    Name resolution for the name <my domain's FQDN> timed out after none of the configured DNS servers responded.

    I believe the DNS server is setup correctly, I can nslookup the domain's FQDN from command line.

    Please help!

    • Moved by Tiger Li Tuesday, June 29, 2010 5:07 AM (From:Windows Server 2008 R2 General)
    Monday, June 07, 2010 8:28 PM

Answers

  • Hello,

    the domain controller is multihomed which is a not recommended configuration and result in problems as you see now. Please remove all not to the DC/DNS server itself belonging ip addressesn and disable unused NICs. Then run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service or reboot.

    Also installing sharepoint or SQL/ Exchange etc. isn;t recommended. A DC should do it's basic job, AD/DNS/GC and maybe DHCP.

    http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by Tiger Li Monday, June 14, 2010 9:37 AM
    Monday, June 07, 2010 9:29 PM
  • Hello,

    even that it works somehow in the past, you see now problems are rising up and they belong to the multiple ip addresses, as that DC is now listed in the DNS zones with 2 or more records and that confuses each domain member as they aren't able to communicate correct anymore, if you send information to A and get an answer from B this wan't work.

    Basically one option is to disable the registration of the multiple NICs in DNS, but i don't know how this will effect the access options to the sharepoint. You can try if that helps and if not check the setting again. Run ipconfig /flushdns and ipconfig /registerdns and make sure that DNS zones are updated correct.

    A DC should always do it's main job, AD/DNS/GC and maybe DHCP that's it. All other applications should run on member servers. Additional it is recommended to have at least 2 DC/DNS/GC per domain for failover and redundancy. So you should really rethink your design.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by Tiger Li Monday, June 14, 2010 9:37 AM
    Tuesday, June 08, 2010 8:10 AM

All replies

  • check if the computer has the correct dns in the nic (cmd.exe - ipconfig /all). you can also check if you can reach the dns on port 53 or if a firewall is blocking it, eg with cmd.exe - telnet dnsname 53
    Monday, June 07, 2010 8:53 PM
  • Hello,

    please post an unedited ipconfig /all from the DC/DNS server so we can exclude configuration problems.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Monday, June 07, 2010 8:57 PM
  • Here it is. I have to edit out the sensitive parts, because this is a public facing server at a University. I can, however, indicate here how I edited, perhaps this can help

    The server has two active NIC, I left the internal one unedited. I added some comments for explanation.
    The public facing IP is 111.112.113.114, and the hostname is host.domain.school.edu.

    Thank you for your help and understanding.

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : host
       Primary Dns Suffix  . . . . . . . : domain.school.edu
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : domain.school.edu
                                           local

    Ethernet adapter Local Area Connection 4:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #4
       Physical Address. . . . . . . . . : 00-10-18-61-CB-1E
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection 3:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #3
       Physical Address. . . . . . . . . : 00-10-18-61-CB-1C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Cluster:

       Connection-specific DNS Suffix  . : local
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #2
       Physical Address. . . . . . . . . : A4-BA-DB-1D-4B-28
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.1.255.249(Preferred)   # This is statically assigned by the DHCP server on internal cluster, which provides a NAS for this server's backup.
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Lease Obtained. . . . . . . . . . : Sunday, June 06, 2010 11:13:13 AM
       Lease Expires . . . . . . . . . . : Monday, June 07, 2010 2:27:37 PM
       Default Gateway . . . . . . . . . : 10.1.1.1    # This is the frontend of the cluster, which has DHCP, DNS, NAT.
       DHCP Server . . . . . . . . . . . : 10.1.1.1
       DNS Servers . . . . . . . . . . . : 10.1.255.249
                                           10.1.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter SharePoint:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)
       Physical Address. . . . . . . . . : A4-BA-DB-1D-4B-26
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 111.112.113.114(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 111.112.113.1
       DNS Servers . . . . . . . . . . . : 111.112.113.114
                                           111.112.128.1   # This is the school's DNS server. This server (host.domain.school.edu is authoritative for the domain.school.edu zone)
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.local:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : local
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{237E8C77-0D87-4FC7-891B-019308639405}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{0A5F0034-564F-4FAB-B1F6-A13FAA731A8F}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{D0AD3538-76DB-4D65-A880-CAA23A2E142F}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter 6TO4 Adapter:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft 6to4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:a443:1af1::a443:1af1(Preferred)
       Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
       DNS Servers . . . . . . . . . . . : 111.112.113.114
                                           111.112.128.1
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Monday, June 07, 2010 9:22 PM
  • Hello,

    the domain controller is multihomed which is a not recommended configuration and result in problems as you see now. Please remove all not to the DC/DNS server itself belonging ip addressesn and disable unused NICs. Then run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service or reboot.

    Also installing sharepoint or SQL/ Exchange etc. isn;t recommended. A DC should do it's basic job, AD/DNS/GC and maybe DHCP.

    http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by Tiger Li Monday, June 14, 2010 9:37 AM
    Monday, June 07, 2010 9:29 PM
  • Thank you for your answer.

    Our group has only one server, whose main function is the SharePoint server. It also needs to have AD for MOSS. I can try removing the multihome, but that didn't seem to cause us any problem for our previous server, which has (to my knowledge) identical software configuration.

    Monday, June 07, 2010 10:22 PM
  • Hello,

    even that it works somehow in the past, you see now problems are rising up and they belong to the multiple ip addresses, as that DC is now listed in the DNS zones with 2 or more records and that confuses each domain member as they aren't able to communicate correct anymore, if you send information to A and get an answer from B this wan't work.

    Basically one option is to disable the registration of the multiple NICs in DNS, but i don't know how this will effect the access options to the sharepoint. You can try if that helps and if not check the setting again. Run ipconfig /flushdns and ipconfig /registerdns and make sure that DNS zones are updated correct.

    A DC should always do it's main job, AD/DNS/GC and maybe DHCP that's it. All other applications should run on member servers. Additional it is recommended to have at least 2 DC/DNS/GC per domain for failover and redundancy. So you should really rethink your design.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    • Marked as answer by Tiger Li Monday, June 14, 2010 9:37 AM
    Tuesday, June 08, 2010 8:10 AM
  • you can try to clear the default gateways from all but the internal nic as a first try
    Tuesday, June 08, 2010 8:31 AM
  • On July 1st we will be making Windows Server 2008 R2 General forum read only. After receiving a lot of feedback from the community, it was decided that this forum is a duplication and therefore redundant of the General Forum. So, until July 1st, we will start asking customers to redirect their questions to the General Forum. On June 11th, CSS engineers will move any new threads to the General Forum.

     

    Please post a reply to the announcement thread if you have any feedback on this decision or the process. You can also email WSSDComm@microsoft.com.


    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.
    Tuesday, June 29, 2010 5:07 AM