JSI Tip 1135. DNS won't start due to incorrect EnableRegistryBoot value.

Jerold Schulman

March 9, 1999

1 Min Read
ITPro Today logo in a gray background | ITPro Today


When you restart your DNS server, you may receive one or more of the following event log entries or error messages:

   The RPC Server is unavailable. (in DNS Manager)   Event ID: 157   Source: DNS   Description: DNS Server is not root authoritative and no cache file specified.   A cache file must be specified when the DNS server is not authoritative for   the root domain. The cache file must contain NS record(s) for root DNS   servers and corresponding A record(s) for the root DNS servers. Otherwise,   the DNS server will be unable to contact the root DNS server on startup and   will be unable to answer queries for names outside of its own authoritative   zones.   Event ID: 7023   Source: Service Control Manager   Description: The Microsoft DNS Server service terminated with the following   error: The system cannot find the file specified.   Event ID: 3   Source: DNS   Description: The DNS Server has shutdown.

The EnableRegistryBoot value is probably incorrect.

Use Regedt32 to navigate to:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesDnsParameters

Double-click the EnableRegistryBoot value name, in the right hand pane.This type REG_DWORD value has two possible values:

0 - Boot DNS from a boot file.

1 - Boot DNS from the registry.

When you create the first zone, the boot files information is migrated to the registry and EnableRegistryBoot is set to 1.

If DNS won't boot from the registry, set the value to 0.

You may need to copy the backup boot file from

%SystemRoot%System32DnsBackup to %SystemRoot%System32Dns.

Start the DNS service.

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like