The DNS server is now booting from the registry. The existing server boot file will no longer be read by the DNS server at startup. For any new zones that you add or for changes you make to zone information, you must make them using DNS Manager. The previous DNS server boot file has been moved to the %SystemRoot%\\System32\\Dns\\backup directory. To return to using the server boot file, you must perform the following: (1) Open the Registry Editor (Regedt32.exe), (2) navigate to the DNS server registry location: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\DNS\\Parameters, (3) delete this value: EnableRegistryBoot, and (4) recopy or create the server boot file to be used by the DNS Server in the %SystemRoot%\\System32\\Dns directory. If you revert to booting the server from file, all prior changes to zone information (including any new zones you might have added) that were made while using DNS Manager are lost.

Details
Product: Windows Operating System
Event ID: 2000
Source: DNS
Version: 5.0
Symbolic Name: DNS_BOOTFILE_BACKUP_MESSAGE
Message: The DNS server is now booting from the registry. The existing server boot file will no longer be read by the DNS server at startup. For any new zones that you add or for changes you make to zone information, you must make them using DNS Manager. The previous DNS server boot file has been moved to the %SystemRoot%\\System32\\Dns\\backup directory. To return to using the server boot file, you must perform the following: (1) Open the Registry Editor (Regedt32.exe), (2) navigate to the DNS server registry location: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\DNS\\Parameters, (3) delete this value: EnableRegistryBoot, and (4) recopy or create the server boot file to be used by the DNS Server in the %SystemRoot%\\System32\\Dns directory. If you revert to booting the server from file, all prior changes to zone information (including any new zones you might have added) that were made while using DNS Manager are lost.
   
Explanation

If you see this in conjunction with event ID 157 or event ID 7023 from the Service Control Manager, this might indicate that the registry key which determines whether your DNS initializes from a boot file or from the registry might not have been updated properly.

   
User Action

Edit an entry in the registry, and if your DNS server initializes from a boot file, you might need to copy a new boot file into the DNS folder.

Caution:
Do not use a registry editor to edit the registry directly unless you have no alternative. The registry editors bypass the standard safeguards provided by administrative tools. These safeguards prevent you from entering conflicting settings or settings that are likely to degrade performance or damage your system. Editing the registry directly can have serious, unexpected consequences that can prevent the system from starting and require that you reinstall Windows 2000. To configure or customize Windows 2000, use the programs in Control Panel or Microsoft Management Console (MMC) whenever possible.

Start a registry editor (regedt32.exe or regedit.exe), and then locate the following subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dns\Parameters.

Edit the entry EnableRegistryBoot (data type: REG_DWORD) so that the value is 1 for registry boot or 0 for boot file. Exit the registry editor. The value of this entry was set to 1 when the first zone was created, and by default the boot file’s information was then migrated into the registry. When you reset this entry back to zero, it disables the DNS server from booting or initializing from the registry. If the DNS server does not boot from the registry, it must initialize from a boot file. A backup boot file can be found in the following location:

Systemroot\System32\Dns\Backup. Copy this file to the Dns folder, and then start DNS.

Related:

Leave a Reply