Zone Transfers Are Incomplete When Deleting a Delegation

If you delete a delegation from the parent zone on the primary Domain Name System (DNS) server, secondary DNS servers do not receive the change in the next zone transfer or in any subsequent transfers.

This behavior occurs because deleting the delegation does not increment the Start of Authority (SOA). If a record is added to the parent zone to force an SOA increment, the change is still not sent in the zone transfer.

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

To work around this problem, manually delete the delegation from the DNS zone file on any secondary DNS servers:

1. Stop the DNS server service on the secondary DNS server.
2. Locate the %SystemRoot%/System32/Dns folder.
3. Open the the zone file (for example, filename.com.dns) in Notepad.
4. Delete the NS and A records for the delegation.
5. Save the zone file with the same name.
6. Restart the DNS server service.

NOTE: You can also simply delete the zone file and allow a new zone transfer containing the updated zone information to occur.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.