Lack of Secondary Address May Cause DNS Service to Hang (164982)
The information in this article applies to:
- Microsoft Windows NT Server 4.0
This article was previously published under Q164982 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:
- From the DNS Manager, select your zone, right click, then click
Properties.
- 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):
Modification Type: | Major | Last Reviewed: | 8/9/2001 |
---|
Keywords: | kbbug KB164982 |
---|
|