Article ID: 129047
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q129047
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
Windows NT 4.0 imports Domain Name Service (DNS) information from boot
files into the registry when data is modified using DNS Manager. However,
after it is there, the information is maintained and updated only in the
registry. If data is changed using DNS Manager, the information is not
written back to the original boot file.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or 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:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has designed a hotfix for the DNS service that causes it to
automatically write back to boot files any changes in the registry that
affect information stored in boot files (such as new zones, change files,
change zone types, change master, change forwarders, and so on).
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.
If you want to enable Windows NT to store and track DNS information in boot
files, apply the above hotfix and use Registry Editor to delete the value
EnableRegistryBoot from following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
You can now replace your desired boot file in the %SystemRoot%\System32\Dns
folder. During startup, the DNS service now reads from the boot file first,
overriding any settings in the registry. After the boot file has been
processed, secondary information not found in the boot file is loaded from
the registry (secondary security, notify lists, forwarding timeouts, listen
IP list, and so on).
WARNING: Initially, when you configure Windows NT to read and write DNS
settings to the boot files, any changes made in the registry through DNS
Manager that are not present in the boot files are lost. After making the
above registry change, all new changes made through DNS Manager are written
to the boot files.
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB129047