The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.0.4.

5 pts.
Tags:
DNS errors
DNS server
UDP
UDP port
User Datagram Protocol
Windows Server 2003
i have two dns servers on our network, (windows server 2003 standard); (a) the dns server1, (has both forward lookup and reverse lookup zones configured), to which all hosts on the network are pointed, this same server has forwarders configured, pointing to our dns server2.  (b) the dns server2 has only reverse lookup zone configured. the dns server2 also has forwarders configured pointing to a public dns server. i have a problem on the dns server2,that has only the reverse lookup zone configured. It has forwarders to a public dns server. suddenly one morning it, it started, but it could not resolved hostnames. i checked the events log, and discorvered that it  logs two errors, ( it logs this same errors each time you attempt starting the dns server), any time the dns service starts, the errors are; The DNS server could not open socket for address 192.168.0.4. 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 DNSParmeters 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.   the second error; The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.0.4. The event data is the error code. Restart the DNS server or reboot your computer. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. i have tried changing the ip address, (although it did not change in the first place) to the ip address on the nic of the server. i have also tried deleting the value of the listening address in the registry, this also did not work.   kindly help me with your insights, guys. i really need to get this resolved. Thanks a bunch

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi 2temmy,

Besides DNS, what else is this server running?

I had a call few years ago to look at a similar problem.
The problem then was a memory leak because of a crappy Antivirus that happened to catch a virus on that server (it was also a DFS root).
Once the server started a huge amount of resources were being used by the Antivirus preventing DNS to start up correctly.

I recommend you to stop all unnecessary applications and services (at least for testing) and after that try to restart DNS service.
If unsuccessful, restart the server only with minimal system service and see if it started up.

Please post back.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following