Nameserver Setup breaks server, help!

skoker

Member
Jun 8, 2006
13
0
151
I ran the Nameserver setup to see what it did (oops) and if seems to have trashed my whole BIND setup, and named.conf seems to have been deleted. I tried updating cPanel via WHM and recompiling Apache, but it is still down.

Is there any way I can reinstall BIND?

My server is WHM 10.8.0 cPanel 10.8.2-S120
Fedora i686 - WHM X v3.1.0


Thank you!
 

skoker

Member
Jun 8, 2006
13
0
151
Now something is seriously screwed, when trying to log in via SSH, I get:

ssh: ******.com: No address associated with nodename
 

skoker

Member
Jun 8, 2006
13
0
151
If it helps, WHM now gives me this:

Name Server Activated
Ensuring caching-nameserver is installed
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Parsing package install arguments
Nothing to do
Activating name server monitoring (chkservd)
Setting up rndc configuration
!! fixrndc requires a syntactically correct /etc/named.conf.
!! No changes were made to /etc/named.conf. Problem was:
!! /etc/rndc.key:8: unknown option 'default-key'
/etc/rndc.key:9: unknown option 'default-server'
/etc/rndc.key:10: unknown option 'default-port'
/etc/named.conf:222: '}' expected near end of file
Restarting Nameserver
Starting named:
Error in named configuration:
/etc/rndc.key:8: unknown option 'default-key'
/etc/rndc.key:9: unknown option 'default-server'
/etc/rndc.key:10: unknown option 'default-port'
/etc/named.conf:222: '}' expected near end of file
[FAILED]
Restarting chkservd
Stopping chkservd: [ OK ]
Starting chkservd: [ OK ]
 

rootsupport

Member
May 2, 2006
18
0
151
India
Can you provide us the result of the following command:

/scripts/restartsrv named
 

skoker

Member
Jun 8, 2006
13
0
151
Sure:


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


named has failed, please contact the sysadmin (result was "named is not running").
Sep 16 08:27:54 ceratodus named: /etc/rndc.key:8: unknown option 'default-key'
Sep 16 08:27:54 ceratodus named: /etc/rndc.key:9: unknown option 'default-server'
Sep 16 08:27:54 ceratodus named: /etc/rndc.key:10: unknown option 'default-port'
Sep 16 08:27:54 ceratodus named: /etc/named.conf:222: '}' expected near end of file
 

CentaurAtlas

Registered
Dec 27, 2005
3
0
151
My server started the same thing this morning. :) The server has been running nicely for >18 months...

named has failed, please contact the sysadmin (result was "named is not running").
Sep 16 12:13:43 server1 named: failed
Sep 16 12:13:43 server1 named[3544]: starting BIND 9.2.4 -u named
Sep 16 12:13:43 server1 named[3544]: using 1 CPU
Sep 16 12:13:43 server1 named[3544]: loading configuration: failure
Sep 16 12:13:43 server1 named[3544]: exiting (due to fatal error)
Sep 16 12:13:43 server1 named: named startup failed

-------

WHM 10.8.0 cPanel 10.8.2-R119
RedHat Enterprise 3 i686 - WHM X v3.1.0

WHM says:
named has failed, please contact the sysadmin (result was "named is not running"). Sep 16 12:00:19 server1 named: failed Sep 16 12:00:19 server1 named[3043]: starting BIND 9.2.4 -u named Sep 16 12:00:19 server1 named[3043]: using 1 CPU Sep 16 12:00:19 server1 named[3043]: loading configuration: failure Sep 16 12:00:19 server1 named[3043]: exiting (due to fatal error) Sep 16 12:00:19 server1 named: named startup failed

Command line with /usr/sbin/named -g -c /etc/named.conf says:
Sep 16 12:01:51.462 starting BIND 9.2.4 -g -c /etc/named.conf
Sep 16 12:01:51.462 using 1 CPU
Sep 16 12:01:51.466 loading configuration: failure
Sep 16 12:01:51.466 exiting (due to fatal error)

----

When I try to do the up2date, I get the following (which I think is a resolving problem):
up2date install bind-libs
Error communicating with server. The message was:
Name or service not known
-----------
My resolv.conf looks like:
domain <mydomain>.com
nameserver 66.139.72.14
nameserver 66.139.72.20
nameserver <my ip>

-----------
rpm -qa | grep bind shows:
bind-utils-9.2.4-14_EL3
bind-devel-9.2.4-14_EL3
bind-libs-9.2.4-7_EL3
ypbind-1.12-5.21.9
bind-9.2.4-14_EL3

so I am thinking the bind-libs version may be an issue, but up2date isn't resolving (I think) even though the two name servers in resolv.conf are working from what I can tell.

Any ideas? ;-)


---------------------
I'm going to try this:

wget http://216.127.74.88/files/bind-libs-9.2.4-14_EL3.i386.rpm
then
rpm -i bind-libs-9.2.4-14_EL3.i386.rpm

But am a bit nervous about messing it up more!
 
Last edited: