Can not start DNS Server Service

TonyWalker821
TonyWalker821 used Ask the Experts™
on
Hi,

I have a problem with an SBS 2003 machine.  A few days ago the server restarted because of Windows Updates and when it restarted I received a message about some services not being able to start.  I looked in Event Viewer and found an error saying that DNS could not start because there is not enough storage available.  I found that the C drive had run out of space, so I freed up more than 3Gb of space.  I then went back and tried to manually start the service but I receive the error below. I have also attached two further errors found in the DNS log.

Could not start the DNS server service on Local computer.
Error 14: Not enough storage is available to complete this operation

To workaround this I have had to add Hosts files to each PC but I need to find a long term solution, as I have no internet access on the server.
Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	407
Date:		14/07/2008
Time:		12:42:51
User:		N/A
Computer:	ALPHA
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.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 26 27 00 00               &'..    
 
 
Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	408
Date:		21/07/2008
Time:		15:36:51
User:		N/A
Computer:	ALPHA
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\Parmeters\ 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.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Chris DentPowerShell Developer
Top Expert 2010

Commented:

Silly question, but I'm going to ask it anyway.

You have rebooted again since making space, right?

Chris

Author

Commented:
Yes :)
Chris DentPowerShell Developer
Top Expert 2010

Commented:

hehe had to check, you know how it is :)

Can you use this to see if anything is listening on Port 53 at the moment?

netstat -an | FindStr 53

The DNS service normally listens on localhost like this:

TCP  127.0.0.1:53           *:*
UDP    127.0.0.1:53           *:*

You should also find similar entries for the other IP addresses on the system.

Finally, it's possible that a third party bit of software is trying to start up the service for a second time. That would cause an overlap as the port is already in use. You don't have anything to keep an eye on services with the server do you?

Chris
Announcing the Winners!

The results are in for the 15th Annual Expert Awards! Congratulations to the winners, and thank you to everyone who participated in the nominations. We are so grateful for the valuable contributions experts make on a daily basis. Click to read more about this year’s recipients!

Author

Commented:
I have
UDP    127.0.0.1:53       *.*
but no entry for TCP
Chris DentPowerShell Developer
Top Expert 2010

Commented:

Okay, TCP is less important in this case. It's used for UDP overflow and zone transfers, not regular queries.

Is the DNS Service listed as Started at the moment?

Can you try:

nslookup
server 127.0.0.1
www.google.com

Just to see if it's actually responding on that?

Chris
Hi Chris,

I think I know what the problem is.  If I uninstall Windows Update KB951746 then restart the server all is ok.  I found an article on EE about this possibly causing a problem.  Do you know why this would happen and what I can do to prevent this, apart from turning of Windows Updates. Do I need this update?

Thanks,
Chris DentPowerShell Developer
Top Expert 2010
Commented:

Yeah, there have been a significant number of problems with that patch.

It is a major change to DNS, it makes the DNS service sit on 2500 randomly generated ports (all high-numbered ports).

In your case you might find that you have something occupying one of the ports it's trying to acquire.

It is possible to set the range which may well resolve this, that's detailed here:

http://support.microsoft.com/kb/953230

You wouldn't be the first to have to uninstall it though.

Chris

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial