Domain Name System Zone Transfer May Not Work Over Dial-On-Demand Connection (232186)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

A Domain Name System (DNS) zone transfer over a dial-on-demand (DOD) connection may not work. This problem may occur under any of the following situations:

When you create a secondary zone.
When a primary DNS server sends a notification for the secondary DNS server to initiate a zone transfer.

CAUSE

This problem can occur if the poll for the Start of Authority (SOA) record from the secondary DNS server times out before the DOD connection is established.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem:

Use Registry Editor (Regedt32.exe) to view the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
Add the following registry value to this key
Value Name: XfrConnectTimeout
Value Type: REG_DWORD
Value Data: XXX
where XXX is the number of seconds that the DNS server waits before timing out a zone transfer. The default value is 30 seconds.

MORE INFORMATION

Configure the XfrConnectTimeout registry value on every DNS server that performs zone transfers over a DOD connection.

For additional information about DNS zone transfers, click the article number below to view the article in the Microsoft Knowledge Base:

164017 Explanation of a DNS Zone Transfer