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

    Question

  • I am running a single server 2k8 r2 domain controller / dns server,

    On initial boot i always get this error...

    Name resolution for the name _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.lightspeeders.local timed out after none of the configured DNS servers responded.

     

    The dns in network config points to itself

     

    I understand this is due to the dns being called up on the server while it is booting and as such hasnt loaded it yet.

     

    Do i really need to get another server running dns to stop this error showing up? or is there a way around this (maybe delay the dns call so dns loads up before hand?)

     

    Thank you in advance

     

    Timez82

    • Moved by Miles LiModerator Wednesday, June 30, 2010 9:28 AM (From:Windows Server 2008 R2 General)
    Saturday, June 19, 2010 6:32 PM

Answers

  • please help :(


    Hello,

    what you see is expected as long as no DNS server is available during boot of a DC. The best option is to have always a DNS server up and running and never boot all DC/DNS servers together. Also it is recommended to have at least 2 DC/DNS/GC per domain for failover and redundancy reason.

    AD relies on the netlogon service, which relies on the DNS server and when you use AD integrated DNS zones, AD has to run. This result in longer boot times.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Sunday, June 20, 2010 12:25 PM

All replies

  • Hello Timez82,

    You do not need another server running dns.

    You can delay the  Netlogon service to ensure that the DNS Server service is up and running for Dynamic DNS registration and query for existing Active Directory domain controllers that are in the DNS server database.

    How to delay loading of specific services
    http://support.microsoft.com/kb/193888

    Best regards,
    Harry

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, June 19, 2010 7:20 PM
  • Can you log in and look at the Event Logs for (Directory Service, DNS, etc)?  Let us know if anything else is popping up in there.  You should be able to get this working with a single DC/DNS server no problem.  You don't want to delay DNS as it is required for the DC to get going.

    Here is a good link of things to troubleshoot: http://technet.microsoft.com/en-us/library/cc961921.aspx

     


    Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com
    Saturday, June 19, 2010 7:24 PM
  • Making netlogin depend on dns worked perfectlly - thank you :)

    I am also getting this under dns (this was happining before the fix and still does)...

     

    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

     

     

    (i dont want to delay anything unless told in case i make the server unbootable)

    Saturday, June 19, 2010 8:28 PM
  • Is IPv6 enabled?  If so, disable, reboot, and see if that clears it up.  Did you ever try to make this server part of another domain?  Any other error events in the DNS log?  What happens is you restart the DNS service, any errors after that? 


    Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com
    Saturday, June 19, 2010 8:43 PM
  • I had already disabled IPv6 on the network card - and have now also done so in the registry -

    same error

     

     

    no never tried to add this server to a different domain - its a fresh install

     

    no other errors in the event log for dns

     

    restaring both the dns server/client services make no error - so this is just on boot up

    Saturday, June 19, 2010 9:11 PM
  • please help :(
    Saturday, June 19, 2010 10:25 PM
  • Here is a similar post...suggest using a Host file.  Makes sense for a single DC environment.  Does this help?  Still looking for other options.

    http://social.technet.microsoft.com/Forums/en/winserverDS/thread/ff936f70-780d-486e-a808-35d9e7fc0ddb

     


    Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com
    Saturday, June 19, 2010 11:59 PM
  • please help :(


    Hello,

    what you see is expected as long as no DNS server is available during boot of a DC. The best option is to have always a DNS server up and running and never boot all DC/DNS servers together. Also it is recommended to have at least 2 DC/DNS/GC per domain for failover and redundancy reason.

    AD relies on the netlogon service, which relies on the DNS server and when you use AD integrated DNS zones, AD has to run. This result in longer boot times.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Sunday, June 20, 2010 12:25 PM