Event Id | 410 |
Source | Microsoft-Windows-DNS-Server-Service |
Description | "The DNS server list of restricted interfaces does not contain a valid IP address for the server computer. The DNS server will use all IP interfaces on the machine. Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. " |
Event Information | According to Microsoft : Cause : This event is logged when DNS server list of restricted interfaces does not contain a valid IP address for the server computer. Resolution : Correct the network interface problem On computers with more than one network interface, the DNS server can be configured to respond to Domain Name System (DNS) requests on one or more of the interfaces. If the list of interface addresses is not correct, the DNS server is not able to respond to requests from other computers on the network. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To correct the IP addresses that the DNS server is configured to use: 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.On the Interfaces tab, ensure that All IP addresses is selected, or determine whether any address in the IP addresses list is not valid for the server's network interfaces. 5.Clear the check box next to any invalid addresses, and then click OK. 6.Right-click the DNS server, click All Tasks, and then click Restart. 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 410 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.