| Event Id | 1200 |
| Source | Microsoft-Windows-DNS-Server-Service |
| Description | The DNS server could not find or open the boot file %1. This file must be called Boot, and it must be located in the %SystemRoot%\System32\Dns directory. |
| Event Information | According to Microsoft : Cause : This event is logged when DNS server could not find or open the boot file. Resolution : Replace the boot file with a backup copy The DNS Server service can be configured to read initialization information from a boot file. If this file is missing or corrupt, the DNS Server service cannot start properly. To restart the DNS Server service:: 1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager. 2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS. 3Right-click the DNS server, click All Tasks, and then click Restart. If the problem continues, restart the computer, and then use Server Manager to confirm that the DNS Server service has started. To restart the computer: Click Start, click the arrow next to the Lock button, and then click Restart. To confirm that the DNS Server service has started: 1.On the DNS server, start Server Manager. 2.In the console tree, expand Roles, and then click DNS Server. The System Services list shows the state of the DNS Server service. Verify To verify that the Domain Name System (DNS) configuration is correct, verify that all configuration settings are correct, check the event log for events that indicate continuing problems, and then verify that DNS client computers are able to resolve names properly. To verify DNS configuration settings: 1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager. 2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS. 3.Right-click the DNS server, and then click Properties. 4.Review the settings on each tab, and verify that they contain the intended values. 5.Expand the DNS server. 6.Expand a zone folder, right-click a zone, and then click Properties. 7.Review the settings on each tab, and verify that they contain the intended values. 8.Repeat steps 6 and 7 for each zone. To verify that DNS client computers can resolve names properly: 1.On a DNS client computer, open a command prompt. To open a command prompt, click Start, click Run, type cmd, and then click OK. 2. At the command prompt, type pinghostname (where hostname is the DNS name of a computer with a known IP address), and then press ENTER. If the client can resolve the name, the ping command responds with the following message: Pinging hostname [ip_address] Note: The name resolution is successful even if the ping command reports that the destination is unreachable. If the client cannot resolve the name, the ping command responds with the following message: Ping request could not find host hostname |
| Reference Links | Event ID 1200 from Microsoft-Windows-DNS-Server-Service |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.