The DNS service takes a long time to start on a DNS server that is running Windows Server 2012

Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 Essentials


Consider the following scenario:
  • You have a Domain Name System (DNS) server that is running Windows Server 2012.
  • You have hundreds of Active Directory-Integrated DNS Zones configured on the DNS server.
  • The domain naming master server is temporally down.
  • The DNS service is started.

In this scenario, it may take a long time (for example, several hours) for the DNS service to restart.


For each zone to be loaded, the DNS Server service tries to connect to the domain controller that has the Active Directory domain naming operations master role and waits until the TCP connection attempt times out. By default, it takes about 21 seconds for each call to fail. If there are hundreds of zones configured, the time-out for each such connection accumulates, and it takes a long time for the DNS service to restart.


Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must have Windows Server 2012 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See the terminology Microsoft uses to describe software updates for more information.