View Single Post
  #5  
Old 9th March 2006, 13:11
spaz spaz is offline
Junior Member
 
Join Date: Mar 2006
Posts: 4
Thanks: 0
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by falko
Do I uderstand you right that you have a symlink /etc/bind/bind
Ok, fixed that newbie mistake! now linking /etc/bind ->
Should it be a soft link? I used "ln" without the -s flag.

After fixing some more permissions on directories (some were 700, changing to 775 and changing group root to bind in relevant subdirectories under /var), I get the following in the logs at startup attempt:

05:53:26 serv named[925]: starting BIND 9.2.4 -u bind -t /var/lib/named
05:53:26 serv named[925]: using 1 CPU
05:53:26 serv named[925]: loading configuration from '/etc/bind/named.conf'
05:53:26 serv named[925]: listening on IPv4 interface lo, 127.0.0.1#53
05:53:26 serv named[925]: listening on IPv4 interface eth0, 192.168.1.4#53
05:53:26 serv named[925]: command channel listening on 127.0.0.1#953
05:53:26 serv named[925]: command channel listening on ::1#953
05:53:26 serv named[925]: couldn't open pid file '/var/run/bind/run/named.pid': No such file or directory

05:53:26 serv named[925]: exiting (due to early fatal error)


Note that /var/run/bind/run/ is empty. Should I "touch" named.pid in /var/run/bind/run/ and if so, what permissions and user/group? Or will this file be created on its own when bind runs? I tried both ways, with directory empty and touching file with 664 root/bind named.pid file, and the error message in logs was same as above.

Just in case it matters, I only have port 53 forwarded from router, and port 53 open on firewall, do not have port 953 open on firewall or forwarded from router.

Thanks so far, a bit of progress.
Reply With Quote