Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Domain Controller boots up slowly when pointing to itself as the only DNS server


View products that this article applies to.

Source: Microsoft Support

↑ Back to the top


Rapid publishing

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


Result



The Windows Server 2003 domain controller boots up very slowly. It may take more than 15 minutes for the domain controller to boot up.

This may occur when the following situations are true:

1. There are several domain controllers in the forest.
2. The Domain Controller is a DNS server.
3. The server points to itself as the DNS server, and no secondary DNS server is configured.

↑ Back to the top


Cause



Windows Server 2003 domain controllers would try a replication first when booting up. This depends on DNS. When the DNS server service is also installed on the domain controller, it tries to load Active Directory integrated zones. However, since the intial replication is not finished, this fails too.

Therefore, when the Domain Controller points to itself as the only DNS server, the problem occurs when the computer reboots.

↑ Back to the top


Resolution

To resolve this issue, point the Domain Controller to at least two DNS servers.

Option 1: Point it to use a remote DNS server as the preferred DNS server, and use itself as the secondary DNS server.

Option 2: Point to itself as the preferred DNS server, and use another DNS server as the secondary DNS server.

You may refer to the documents listed in the "More Information" section about the best practices for DNS setting.

↑ Back to the top


Moreinformation



Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=KB;EN-US;825036

DNS Server becomes an island when a domain controller points to itself for the _msdcs.ForestDnsName domain
http://support.microsoft.com/default.aspx/kb/275278/


Keywords: Init Syncs advertisement delay hang hangs preparing network connection preparing network connections Applying computer settings

↑ Back to the top


Disclaimer

MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

↑ Back to the top


Keywords: KB945765, kbrapidpub, kbnomt

↑ Back to the top

Article Info
Article ID : 945765
Revision : 1
Created on : 11/30/2007
Published on : 11/30/2007
Exists online : False
Views : 352