DNS Server Event ID 407, 408.

The DNS server refuses to start at times. Or the Event ID 404, 407 and 408 are generated.

Details of the Event ID are given Below:

Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Date: 3/5/2009 12:03:00 PM
Event ID: 408
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DC1-NY-2K8.psytrix.local
Description:
The DNS server could not open socket for address 127.0.0.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 (e.g. another DNS server) is running that would attempt to use the DNS port.
For more information, see "DNS server log reference" in the online Help.

Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Date: 3/5/2009 12:03:00 PM
Event ID: 407
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DC1-NY-2K8.psytrix.local
Description:
The DNS server could not bind a User Datagram Protocol (UDP) socket to 127.0.0.1. The event data is the error code. Restart the DNS server or reboot your computer.

Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Date: 3/5/2009 12:03:00 PM
Event ID: 408
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DC1-NY-2K8.psytrix.local
Description:
The DNS server could not open socket for address 192.168.1.151.
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 (e.g. another DNS server) is running that would attempt to use the DNS port.
For more information, see "DNS server log reference" in the online Help.

Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Date: 3/5/2009 12:03:00 PM
Event ID: 407
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DC1-NY-2K8.psytrix.local
Description:
The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.1.151. The event data is the error code. Restart the DNS server or reboot your computer.

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 404
Date: 3/5/2009
Time: 1:08:24 PM
User: N/A
Computer: DC1-NY-2K8.psytrix.local
Description:
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 127.0.0.1. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 404
Date: 3/5/2009
Time: 1:08:24 PM
User: N/A
Computer: DC1-NY-2K8.psytrix.local
Description:
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 192.168.1.151. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.

This is caused by another process using port 53 (TCP / UDP). To verify this do the following:

net stop DNS (i.e. If it is not already stopped)

netstat –ano find “:53” the output should be something like:

TCP 127.0.0.1:53 0.0.0.0:0 LISTENING 2752
TCP 192.168.1.151:53 0.0.0.0:0 LISTENING 2752
TCP [::1]:53 [::]:0 LISTENING 2752
UDP 127.0.0.1:53 *:* 2752
UDP 192.168.1.151:53 *:* 2752
UDP [::1]:53 *:* 2752

In the output the last digit indicates the PID of the process using the port. Open up the Task Manager and add the PID (Process Identifier) to the process column (how: go to View > Select Columns ).

Once you have located the PID, finding which service / process is using Ports TCP 53 / UDP 53, should be a breeze.

Then just stop the respective process and restart the DNS server service. And the Event IDs will go away.

NOTE: If only the UDP 53 is in use by another process but the TCP 53 port is not, then DNS will start but will still give the same Event ID. However if both TCP 53 and UDP 53 are in use DNS will sometimes not start at all.