Results 1 to 4 of 4
I inherited a suse based dns server. Unfortantly it appears to be running I believe on suse 9.2 or 9.3 home edition stripped of gui desktop (so I have been ...
- 11-25-2008 #1Just Joined!
- Join Date
- Nov 2008
- Posts
- 4
named.pid exists!
I inherited a suse based dns server. Unfortantly it appears to be running I believe on suse 9.2 or 9.3 home edition stripped of gui desktop (so I have been told). Everything had been working just fine for a little over a year and then suddenly it stopped working. I am seeing two problems currently that I do not think are related to each other. The first is that evidentialy, the Primary was not updating the secondary dns server. The other problem (and most obvious one to fix first) is that this box boots up and appears to be working except that dns (bind) is not doing its job. My only real clue at this time is the warning message on boot that says:
Starting name server Bind9 -warning: /var/run/named/named.pid exists! done
Is this something as simple as removing the named.pid so that when it boots it does not find one in that location or is this a deeper problem? I do not have a lot of linux background - as you can probably tell. Any hints or advice would be appreciated. I can connect to the box through telnet and the network cards lights are all correctly lit so I don't see how the card is being faulty.
- 11-28-2008 #2Just Joined!
- Join Date
- Nov 2008
- Posts
- 4
bump
no one knows a thing about using suse as a dns server or about Bind?
- 12-01-2008 #3Just Joined!
- Join Date
- Nov 2008
- Posts
- 4
bump - bump
- 12-02-2008 #4Just Joined!
- Join Date
- Nov 2008
- Posts
- 4
This post can be closed/removed. I was able to find some help over at the Open Suse forums and the Ubuntu forums.


