| Event Id | 800 |
| Source | Microsoft-Windows-DNS-Server-Service |
| Description | The zone %1 is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates. |
| Event Information | According to Microsoft : Cause : This event is logged when the zone is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. Resolution : Correct the zone SOA configuration problem The DNS Server service cannot locate the server that is identified as the start of authority (SOA) for the zone. You must correct the SOA configuration of the zone. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To correct a zone SOA configuration problem: 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.Click Start of Authority (SOA), and then ensure that the correct server is listed in Primary server. If you change any values on this tab, click Increment to ensure that the changes will be propagated to other authoritative servers. 5.Click Name Servers, and then ensure that each server in the list is matched with its IP address. If not, click Add to specify the correct IP addresses for the server. 6.Click OK. 7.In the right pane, verify that the zone contains a host (A or AAAA) resource record for the primary server. 8.If the zone does not contain a host resource record for the primary server, right-click the zone, click New Host (A or AAAA), type the name of the primary server in Name (uses parent domain if blank), type the IP address of the primary server in IP address, and then click Add Host. 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 800 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.