DNS INT Zone File Identified as Reverse Instead of Forward After Applying WinNT 4.0 SP4

ID: Q239079

The information in this article applies to:

Microsoft Windows NT Server versions 4.0 SP4, 4.0 SP5
Microsoft Windows NT Server, Enterprise Edition versions 4.0 SP4, 4.0 SP5

SYMPTOMS

After you update a DNS server with INT zone file(s) containing WINS Lookup record(s) in Windows NT Server 4.0 Service Pack 4, the DNS service does not start and the System Event log contains the following entries:

Event ID 1501 "DNS Server could not parse database file %1 for zone %2.
Event ID 1503 "DNS Server could not parse database file %1 line %2.

You receive the following error messages if you start the DNS Service from an MS-DOS command prompt:

The Microsoft DNS Server service is starting.
The Microsoft DNS Server service could not be started.
A system error has occurred.
System error 13 has occurred.
The data is invalid.

CAUSE

This problem occurs if the zone file does not contain WINS Lookup records. The DNS service may start, but the zone is treated as Reverse. As a result, name resolution of hosts contained in the zone do not resolve and it may not be possible to add new records to the zone file using the DNS user interface. This is because the INT zone file was not recognized as Forward when the DNS service was started.

RESOLUTION

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/windows/servicepacks/

Q152734 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:

http://www.microsoft.com/support/supportnet/overview/overview.asp

STATUS

Microsoft has confirmed this to be a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 6.

Additional query words:

Keywords : kbbug4.00 kbfix4.00 NT4SP6Fix
Version : winnt:4.0 SP4,4.0 SP5
Platform : winnt
Issue type : kbbug