Problem with named reload

JohnyByk

Verified User
Joined
Mar 7, 2012
Messages
251
Welcome.

I have a problem with named settings reload. Changes in the domain does not bring success. Only when named is manually restart (Show Services) everything works fine.

The problem appear after updating libxml12.

The log is empty (when i save domain settings or reload named from Services).

Please help :)
Sorry for my English.
 
Error log is empty.

In DA syslog:
2012:03:07-23:08:04: named reloaded

I'm sure so this have no effect. New domains (added from DA) works after restart (from service monitor), reload is not enough (probably reload dosen't work but i don't know why in log is this information)

My actual version of named is from here:
http://www.directadmin.com/named.debian
 
Have you tried reloading BIND (Berkeley Internet Named Daemon) from the command line? Do you get any errors?

Jeff
 
Yes. I do not know why I did not check this before.
Error:
root@selserv:~# /etc/init.d/named reload
cat: /var/run/bind/run/named.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

It's look like problem with path to named.pid (to /var/run/named/named.pid
After change pid location in named script i have new informations:
Mar 8 01:19:17 selserv named[7930]: received SIGHUP signal to reload zones
Mar 8 01:19:17 selserv named[7930]: loading configuration from '/etc/bind/named.conf'
Mar 8 01:19:17 selserv named[7930]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Mar 8 01:19:17 selserv named[7930]: using default UDP/IPv4 port range: [1024, 65535]
Mar 8 01:19:17 selserv named[7930]: using default UDP/IPv6 port range: [1024, 65535]
Mar 8 01:19:17 selserv named[7930]: none:0: open: /etc/bind/rndc.key: permission denied
Mar 8 01:19:17 selserv named[7930]: couldn't add command channel 127.0.0.1#953: permission denied
Mar 8 01:19:17 selserv named[7930]: none:0: open: /etc/bind/rndc.key: permission denied
Mar 8 01:19:17 selserv named[7930]: couldn't add command channel ::1#953: permission denied
Mar 8 01:19:17 selserv named[7930]: reloading configuration succeeded
Mar 8 01:19:17 selserv named[7930]: reloading zones succeeded

Change permission to 644 fix the problem.

Actual log after reload:
Mar 8 01:27:56 selserv named[8162]: received SIGHUP signal to reload zones
Mar 8 01:27:56 selserv named[8162]: loading configuration from '/etc/bind/named.conf'
Mar 8 01:27:56 selserv named[8162]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Mar 8 01:27:56 selserv named[8162]: using default UDP/IPv4 port range: [1024, 65535]
Mar 8 01:27:56 selserv named[8162]: using default UDP/IPv6 port range: [1024, 65535]
Mar 8 01:27:56 selserv named[8162]: reloading configuration succeeded
Mar 8 01:27:56 selserv named[8162]: reloading zones succeeded

It's safe? All can read this file.
Should I worry? Maybe is better way?
 
It wasnt a chmod problem it was an ownership problem. You just exposed all your private keys to the server.
 
Back
Top