Cant start nameserver with freebsd

**wmeyer** · 03-15-2005 12:11 AM

We are running FreeBSD 5.3 and get the following error message whenever we try and run the nameserver.

Any suggestions would be appreciated.

Thanks

Warren
-------------------------------------------

Name Server Activated
Ensuring caching-nameserver is installed
Using package directory: packages-5.3-release
Cannot find package caching-nameserver ...
Activating nameserver monitoring
chkservdStarting Nameserver

Attempting to restart named

Waiting for named to restart....
.
.
.
.
.
.
.
.
.
.
finished.

named status

named has failed, please contact the sysadmin (result was "named is not running").

**malk** · 03-15-2005 02:56 PM

I am having the same problem on my freebsd 5.3 machine (WHM 10.0.0 cPanel 10.0.0-R11) what it looks like is that named isn't in /usr/sbin/ but in /usr/local/sbin/ I tried symbolically linking it, copying it, but the only thing that worked, in the five minutes I futzed with it, was starting it manually with:

host# /usr/local/sbin/named -u bind -c /etc/namedb/named.conf

The WHM says it is not running, but the machine responds to queries.

**lunsfordsm** · 04-21-2005 10:15 AM

Is there an official fix to this problem?

My server has had the same exact problem for the past couple months, and only runs when manually starting it with

/usr/local/sbin/named -u bind -c /etc/namedb/named.conf

This problem resulted from a CPanel update and was only noticed after a reboot.

**malk** · 04-21-2005 12:22 PM

my horrible solution has been to run a cron script every 15 minutes to restart named. i have been really unhappy with this solution, but it has solved 90% of my problems. I am really hopeful for some decent support with 5.3+

Also, when things go really bad. I have found upcp has helped. But not permanently.

**lpmusix** · 05-12-2005 09:11 PM

I posted this as a bug in bugzilla a week or so ago. hopefully it'll be resolved soon

**creos** · 07-06-2005 03:41 PM

Any update? What's the bugzilla bug #

**AndyReed** · 07-06-2005 09:02 PM

BIND and FreeBSD have many problems, if not configured properly. There are so many variables invloved, and every server is unique. There is no "one-size-fits-all" fix.

**AMD64** · 02-22-2006 04:40 PM

Was there a fix for this issue?

I have FreeBSD 4.10 wit latest cPanel and in service status named shows as "named ()" with no version number. After a reboot named failed to start and had to be started manually.

Any solutions for this?

**AndyReed** · 02-22-2006 04:42 PM

Originally Posted by AMD64

Was there a fix for this issue?

I have FreeBSD 4.10 wit latest cPanel and in service status named shows as "named ()" with no version number. After a reboot named failed to start and had to be started manually.

Any solutions for this?

Remove and then re-install BIND.