Forum Moderators: bakedjake

Message Too Old, No Replies

Dns ERROR

dns error on my server plese help me

         

zeybektolga

1:09 pm on May 11, 2005 (gmt 0)

10+ Year Member



Hi...
My DNS Server (BIND) now down.
i try to restart dns with plesk. When i try to restart give this error
;
-------------------------------------
Unable to make action: Unable to manage service by dnsmng: dnsmng:
Service named failed to start

0: /usr/local/psa/admin/htdocs/server/restart_services.php:19
psaerror(string "Unable to make action: Unable to manage service by
dnsmng: dnsmng: Service named failed to start")
---------------------------------------
NOTE: I assume this problem come with plesk 7.5.3 update. Now my web
sites are down.
Please help me...

Romeo

2:29 pm on May 11, 2005 (gmt 0)

10+ Year Member



Try to get more information about what is really happening during start of named, because you will need to understand, if this is a plesk problem or a bind problem:

Try to start named manually and watch the log for messages.
If it does start OK, then check your plesk update for a problem there.
If it does not, then you have a problem in named, which you should fix first. (Did you change anything in your named config and zone environment since last restart?)

Regards,
R.

zeybektolga

3:01 pm on May 11, 2005 (gmt 0)

10+ Year Member



no there is no problem plesk update.
How ý restart or start named service?
Plese type command in ssh

Romeo

3:34 pm on May 11, 2005 (gmt 0)

10+ Year Member



How to restart or start named service?

... this may depend on the setup of your system.
On a Linux SuSE box it is usually "/usr/sbin/rcnamed start" or "... restart", which is actually a link to a start/stop script in /etc/init.d/named.
Don't know how it is on your system.

Regards,
R.

zeybektolga

3:55 pm on May 11, 2005 (gmt 0)

10+ Year Member



ý type restart command but failed :s
# /usr/sbin/rcnamed start
Starting name server BIND9 failed

What ý do this time?

zeybektolga

4:15 pm on May 11, 2005 (gmt 0)

10+ Year Member



this is log when ý type start command...

named[6710]: starting BIND 9.2.3 -u named
named[6710]: using 2 CPUs
named[6712]: loading configuration from '/etc/$
named[6712]: listening on IPv4 interface lo, 1$
named[6712]: listening on IPv4 interface eth0,$
named[6712]: listening on IPv4 interface eth1,$
named[6712]: listening on IPv4 interface eth0,$
named[6712]: listening on IPv4 interface eth1,$
named[6712]: could not configure root hints fr$
named[6712]: loading configuration: file not f$
named[6712]: exiting (due to fatal error)
named[6746]: starting BIND 9.2.3 -u named
named[6746]: using 2 CPUs
named[6748]: loading configuration from '/etc/$
named[6748]: listening on IPv4 interface lo, 1$
named[6748]: listening on IPv4 interface eth0,$
named[6748]: listening on IPv4 interface eth1,$
named[6748]: could not configure root hints fr$
named[6748]: loading configuration: file not f$
named[6748]: exiting (due to fatal error)

Romeo

5:00 pm on May 11, 2005 (gmt 0)

10+ Year Member



loading configuration from '/etc/$
named[6748]: could not configure root hints fr$
named[6748]: loading configuration: file not f$
named[6748]: exiting (due to fatal error)

hmm, your log looks very broken.
And from what the log tells, your named configuration looks broken, too.
You should check all your named config files, starting with the file mentioned in
"loading configuration from '/etc/$"
(which could be /etc/named.conf on some systems)
and then checking/verifying all other files that are referenced from there, especially the root hints file.
Checking the files should include checking ownership and permissions, so that the named would be able to read them.

Regards,
R.

wheel

1:01 pm on May 12, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I had a very similiar error once. It's almost certainly in your file '/etc/named.conf'. Check for typing errors in whatever you just updated. or go to your previous backup and restart bind, just to get you going.