Named Problem

[Immunity]

Hi friends,

I am newbie here. But i have a problem like all newbies.

I installed cPanel a month ago but then named server is crashed. when i write "service named restart" system says "[email protected] [~]# service named restart
Usage: named {start|stop}"

I will write here all problems.

[email protected] [~]# service named start
[email protected] [~]# service named restart
Usage: named {start|stop}
[email protected] [~]# service named start
[email protected] [~]# service named sop
Usage: named {start|stop}
[email protected] [~]# service named stop
cat: /var/run/named.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -[sigspec]

How can i fix that? All sites run now but i can not add new account with WHM. when i add a new account, i can open the site. It resolves and sees the nameservers but sites do not open.

For ex : http://www.caniy.com

I opened a new hosting by WHM i setuped all ns options. But i can open it. I tried other new ones. Problem is going on.

How can i fix that?

Thanks for your helping,

Best Regards;

Cihan KIZILGÜL
http://www.servetr.com

NOTE : server's ip : 217.20.113.142

name servers : ns1.servetr.com / ns2.servetr.com

 

[Immunity]

I need an answer. Please help me about that topic.

 

[tweakservers]

If the domain is resolving properly in DNS, you may wish to check on your Apache if the domains entries are properly setup there. Also, when you try to setup an account in WHM, are you being prompted for any error?

 

[Immunity]

Hi again,

I do not get any error about Apache. I can not start named too. I opened an account yesterday. It didn't resolve. But i looked at it today, it resolves true. Normally, resolving takes maximum 5 minutes. I waited it about 24 hours.


I will show you all commands.

[email protected] [~]# /scripts/updateuserdomains / done, no problem.

[email protected] [~]# service named restart
Usage: named {start|stop} / it is cause, i think. it have to be restart when i write this command.


[email protected] [~]# named -u named / done, no problem.

[email protected] [~]# service named start
[email protected] [~]# service named stop
/etc/init.d/named: line 18: kill: (19571) - No such process
[email protected] [~]# service named start
[email protected] [~]# service named restart
Usage: named {start|stop}



I opened an account by using WHM. Its name is caniy.com . It see our server's ip but i can not get ping replies. When i send ping other sites, i can get reply.

you can look at servetr.com / caniy.com / They are in same server. I live continuously named problem. How can i fix that?

When i write "service named restart", i can not get command's reply like OK or failed.

 

[dafut]

If named isn't starting, it could be due to a number of issues. What I would do is, in SSH, run the following commands:

# tail -f /var/log/messages <enter>​

This will "follow the tail end" of the messages log. Use "Ctrl-z" to put the tail into the background.

Then run:

# service named start <enter>​

Bring the tailed log back into the foreground with:

# fg <enter>​

Look carefully at the messages log. Look at all of the messages. You should see that it loads a configuration ('etc/named.conf'), listens on the interfaces, with their IP addresses and port, and it then loads all of the zones. Make sure all zones are loaded. Look for any error message: this will be your best clue!

A shortcut to this would be to grep (search) the messages log for "named" entries. A simple grep would be:

# grep named /var/log/messages <enter>​

Expect to get a lot of responses. Look for errors. It could be something as simple as a CNAME record duplicating an MX record, for example. Or, it could be an illegal or improper instruction in named.conf.

If you find a consistent error, google it. Find out why that error gets generated. Some errors can be pretty difficult to decipher all by themselves.

Here are the top lines of my named service on start:

Jan 10 22:03:26 vps named[15478]: starting BIND 9.2.1 -u named
Jan 10 22:03:26 vps named: named startup succeeded
Jan 10 22:03:26 vps named[15478]: using 4 CPUs
Jan 10 22:03:26 vps named[15487]: loading configuration from '/etc/named.conf'
Jan 10 22:03:26 vps named[15487]: no IPv6 interfaces found
Jan 10 22:03:26 vps named[15487]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 10 22:03:26 vps named[15487]: listening on IPv4 interface venet0:0, 207.xx.xx.001#53
Jan 10 22:03:26 vps named[15487]: listening on IPv4 interface venet0:1, 207.xx.xx.002#53
Jan 10 22:03:26 vps named[15487]: listening on IPv4 interface venet0:2, 207.xx.xx.003#53
Jan 10 22:03:26 vps named[15487]: listening on IPv4 interface venet0:3, 207.xx.xx.004#53
Jan 10 22:03:26 vps named[15487]: command channel listening on 127.0.0.1#953
Jan 10 22:03:26 vps named[15487]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Jan 10 22:03:26 vps named[15487]: zone thissite.com/IN: loaded serial 2005112101
Jan 10 22:03:26 vps named[15487]: zone thatsite.com/IN: loaded serial 2005072101

Each and every zone (domain) hosted in your DNS Zones should show up as "loaded serial" (represented by "thissite.com" and "thatsite.com" above, as an example).

To see the zones on your server, run this command:

# ls -l /var/named <enter>​

The "domain.tld.db" files listed here should all have a corresponding line in the /etc/named.conf file. You can view the whole named.conf file with the "cat" command:

# cat /etc/named.conf <enter>​

Good luck.

 

[Immunity]

[email protected] [~]# tail -f /var/log/messages
Jan 11 10:34:10 217-20-113-142 named[11690]: binding TCP socket: address in use
Jan 11 10:34:10 217-20-113-142 named[11690]: listening on IPv4 interface eth0:29 , 89.149.197.161#53
Jan 11 10:34:10 217-20-113-142 named[11690]: binding TCP socket: address in use
Jan 11 10:34:10 217-20-113-142 named[11690]: listening on IPv4 interface eth0:30 , 89.149.197.162#53
Jan 11 10:34:10 217-20-113-142 named[11690]: binding TCP socket: address in use
Jan 11 10:34:10 217-20-113-142 named[11690]: listening on IPv4 interface eth0:31 , 89.149.197.163#53
Jan 11 10:34:10 217-20-113-142 named[11690]: binding TCP socket: address in use
Jan 11 10:34:10 217-20-113-142 named[11690]: /etc/named.conf:4: couldn't add com mand channel 127.0.0.1#953: address in use
Jan 11 10:34:10 217-20-113-142 named[11690]: couldn't open pid file '/var/run/na med/named.pid': Permission denied
Jan 11 10:34:10 217-20-113-142 named[11690]: exiting (due to early fatal error)



when i write fg, i got that

Jan 11 09:58:46 217-20-113-142 named[8531]: lame server resolving 'www.resimturk .net' (in 'resimturk.net'?): 208.101.21.249#53
Jan 11 09:58:46 217-20-113-142 named[8531]: lame server resolving 'www.resimturk .net' (in 'resimturk.net'?): 208.101.21.248#53
Jan 11 09:58:52 217-20-113-142 named[9058]: starting BIND 9.2.4 -u bind -c /etc/ named.conf
Jan 11 09:58:52 217-20-113-142 named[9058]: using 1 CPU
Jan 11 09:58:52 217-20-113-142 named[9058]: loading configuration from '/etc/nam ed.conf'
Jan 11 09:58:52 217-20-113-142 named[9058]: /etc/named.conf:1: open: /etc/rndc.k ey: permission denied
Jan 11 09:58:52 217-20-113-142 named[9058]: loading configuration: permission de nied
Jan 11 09:58:52 217-20-113-142 named[9058]: exiting (due to fatal error)
Jan 11 09:58:52 217-20-113-142 named[8531]: lame server resolving 'www.resimturk .net' (in 'resimturk.net'?): 208.101.21.249#53
Jan 11 09:58:53 217-20-113-142 named[8531]: lame server resolving 'www.resimturk .net' (in 'resimturk.net'?): 208.101.21.248#53
Jan 11 09:58:53 217-20-113-142 named[8531]: lame server resolving 'www.resimturk .net' (in 'resimturk.net'?): 208.101.21.249#53
Jan 11 09:58:53 217-20-113-142 named[8531]: lame server resolving 'www.resimturk

 

[Immunity]

i will look at to your examples again. Thank you very much for your interest.

 

[dafut]

Here's your problem:

Jan 11 09:58:52 217-20-113-142 named[9058]: /etc/named.conf:1: open: /etc/rndc.k ey: permission denied
Jan 11 09:58:52 217-20-113-142 named[9058]: loading configuration: permission de nied
Jan 11 09:58:52 217-20-113-142 named[9058]: exiting (due to fatal error)


You've got a permissions problem, by what it looks like.

Permissions for /etc/rndc.key should be "named" for both user and group. In SSH, do this:

# chown named.named /etc/rndc.key​

Might also want to check your /etc/rndc.conf file. Should be owned by root; group should be named.

-rw-r----- 1 root named 1101 Aug 15 2005 /etc/rndc.conf
-rw------- 1 named named 132 Aug 15 2005 /etc/rndc.key​

It's possible that your OS may be different (use different permissions)...if so, check the support forums for that OS. I'm on Red Hat...

 

[naveen3]

thanks it helped me.

chown named.named /etc/rndc.key