| Event Id | 408 |
| Source | Microsoft-Windows-DNS-Server-Service |
| Description | "The DNS server could not open socket for address %1. Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parameters\ ListenAddress value in the services section of the registry and restart.) If this is a valid IP address for this machine, make sure that no other application is running that would attempt to use the DNS port. " |
| Event Information | "According to Microsoft : Cause : This event is logged when DNS server could not open socket for address. Resolution : Correct server IP addresses and interfaces The DNS server is configured to use an network interface that is not valid. You can either choose to allow the DNS server to use all the network interfaces that are installed on the server or you must confirm that the addresses of the selected interfaces are correct. 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. If this was the only IP interface on this computer, the DNS server might not restart as a result of this error. In that case, remove the DNS\Parameters\ListenAddress value in the services section of the registry, and then restart the DNS Server service. To remove the DNS\Parameters\ListenAddress value in the registry: Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data. 1.On the DNS server, start Registry Editor. To start Registry editor, click Start, click Run, type regedit, and then click OK. 2.In the console tree, navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters 3.Right-click ListAddresses, and then click Delete. 4.In Server Manager, right-click the DNS server, click All Tasks, and then click Restart. If all the IP addresses for this computer are valid, make sure that no other application (such as a third-party DNS server) is running that might try to use the Domain Name System (DNS) port. 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 408 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.