| Event Id | 2202 |
| Source | Microsoft-Windows-DNS-Server-Service |
| Description | The DNS server could not write a registry key. The server disk could be full or corrupted or the maximum permissible size for the server registry has been reached. The DNS server will not be able to save server or zone configuration parameters to in the registry unless the problem is fixed. |
| Event Information | According to Microsoft : Cause : This event is logged when DNS server could not write a registry key. Resolution : Reload, restart, or reinstall A zone failed to load properly. If an attempt to reload the zone is unsuccessful, restart the DNS Server service. If the DNS Server service cannot restart, reinstall the Domain Name System (DNS) server role. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. 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.Expand the server hosting the zone that failed to load, and then double-click the folder containing the zone. 4.Right-click the zone, and then click Reload. If the zone still does not load, restart the DNS Server service. 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. 3.Right-click the DNS server, click All Tasks, and then click Restart. If the DNS Server service does not start, reinstall the DNS server role: 1.On the DNS server, start Server Manager, and then click Roles. 2.In Roles Summary, click Remove roles, and then follow the instructions in the wizard to remove the DNS server role. 3.If you are required to restart the computer, after the computer restarts, start Server Manager. 4.In Roles Summary, click Add roles, and then follow the instructions in the wizard to install the DNS server role. 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 2202 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.