Lack of Secondary Address May Cause DNS Service to Hang

• Microsoft Windows NT Server version 4.0

SYMPTOMS

The Domain Name System (DNS) fails with an access violation, and ceases to resolve names.

CAUSE

You check the box "Only allow access from secondaries Included on Notify list" in the zone properties dialog box, but do not have any secondaries listed.

An attempted zone transfer from either a secondary DNS or NSLOOKUP will cause the DNS service to stop responding.

RESOLUTION

To resolve this issue, use one of the following methods:

• Include the address of the secondary servers in the notify list using the following steps:
  
  
  1. From the DNS Manager, select your zone, right click, then click Properties.
  
  
  
  2. Click Notify then add the addresses of the secondary servers to the Notify list.
  
  
  
  -or-



• Obtain the latest Windows NT Service Pack.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Keywords : kbbug4.00 kbfix4.00 nttcp kbfix4.00.sp2 NTSrv
Version : 4.0
Platform : winnt
Issue type : kbbug