Re: DNS and file system messed up...
On 08/07/2011 23:04, Gary Kline wrote:
On Fri, Jul 08, 2011 at 10:01:45AM +0100, Matthew Seaman wrote:
Date: Fri, 08 Jul 2011 10:01:45 +0100
From: Matthew Seaman m.sea...@infracaninophile.co.uk
Subject: Re: DNS and file system messed up...
To: freebsd-questions@freebsd.org
On 08/07/2011 08:25, Doug Hardie wrote:
On 7 July 2011, at 22:58, Gary Kline wrote:
Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file
not found
Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c
/var/named/etc/namedb/named.conf
The first one that fails is looking for /etc/named.conf. The second
one shows its in /var/named/etc/named/named.conf
Those are different locations. I suspect you have named_flags setup
in rc.conf pointing to /etc/namedb/named.conf rather than the right
location. Its also possible that its not set in rc.conf but defaults
in either the rc script or /etc/rc.d/named. On my system it appears
to default in /etc/rc.d/named.
FreeBSD defaults to running named chrooted. /etc/namedb is actually a
symbolic link:
hi matthew,
i found an in-depth post you wrote re mtree yesterday ( 07july ),
but i figured it was over my head in resetting anything i might need
to reset. i was going to write you offlist. decided to ask the
entire list.
% ls -la /etc/namedb
lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ -
/var/named/etc/namedb
so the files referenced are in fact exactly the same file. However, the
flags from the log extract don't look like the defaults to me. (I'm
running the dns/bind98 port, and the equivalent info from the log line
is '-t /var/named -u bind')
i was using bind98 rather than the earlier bind9 which is out of
date. but bind98 gave me troubles with the rndc.key and other, so i
chose to go back with what worked. --first thing is to get this
working with the older bind9. FWIW, both bind9's given me the same
error and failure. i have walked thru the named script to the point
where it creates the symlink. regardless, i cannot understand the
error and failure messages. i only know that my kill -9 and my
initialization by hand work.
Gary, what named related settings do you have in /etc/rc.conf? You
almost certainly don't need anything more than:
named_enable=YES
and perhaps
syslogd_flags=-ss -l /var/named/var/run/log
so named can log to the system syslog.
Hmmm [c]. as you may have seen in my post to Doug H. i only have
--
named_enable=YES
named_program=/usr/local/sbin/named
named_pidfile=/var/run/named/pid
OK. The good news is that the configuration that works for the system
built-in version of named will work for the dns/bind98 port with very
minor changes, if any.
First: where everything should live
/etc/namedb/named.conf --- named's config file
/etc/namedb/master --- zone files this server is master for
/etc/namedb/slave --- zone files this server slaves from
another master (rw by named)
/etc/named/working --- named's working directory (rw by named)
/etc/rndc.conf --- config file for rndc
There are various other files and directories under /etc/namedb which
you may or may not need depending on how you configure named; in any
case, just leave them in their default locations and with the
permissions the system gives them. (You can use mtree(8) to fix them up
if necessary -- but that's a whole other posting)
Now, although named defaults to running chrooted into /var/namedb, you
don't need to mention that path explicitly anywhere in the config. In
fact, you should think about the configuration as if there was no
chrooting happening at all.
Second: rc.conf settings
named_enable=YES
syslogd_flags=-ss -l /var/named/var/run/log
should be all you need to use the built-in version of named.
Third: rndc configuration
Generate a new rndc key and a config file by:
# rndc-confgen /etc/named/rndc.conf
This should create a new file /etc/namedb/rndc.conf preconfigured to
work with the named instance on the localhost. Look at the text of
the file -- commented out there's a chunk of stuff to copy into
named.conf So let's do that.
If the file contains:
# key rndc-key {
# algorithm hmac-md5;
# secret 0ABCDE123+45+67890==;
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { rndc-key; };
# };
Then copy that without the '#' quotes into named.conf In fact, I find
it helps to add a control for access to ::1 as well. So add this text
to /etc/namedb/named.conf:
key rndc-key {
algorithm hmac-md5;
secret 0ABCDE123+45+67890==;
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { rndc-key; };
inet ::1 port 953
allow { ::1; } keys { rndc-key; };
};
Fourth: set up named.conf
As I don't no much about the config you want, I'm going to have to keep
this to generalities.
In the options section you should
Re: DNS and file system messed up...
On Jul 8, 2011, at 9:54 PM, Gary Kline wrote: On Fri, Jul 08, 2011 at 07:27:12AM -0600, Dan Busarow wrote: Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan Dan! I think you fixed something. I haven't figured this out yet, and would be grateful if you could decode this in /var/log/messages:: Jul 8 20:39:32 ethic named[83003]: stopping command channel on :: 1#953 Jul 8 20:39:32 ethic named[83003]: exiting Jul 8 20:39:37 ethic named[84090]: starting BIND 9.3.6-P1 -c /etc/namedb/named.conf -t /var/named -u bind Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Gary, Theres probably an /etc/rc.conf line to fix these but what I always do is simply symlink /etc/namedb/rndc.key to /etc/rndc.key # ln -s /etc/namedb/rndc.key /etc/rndc.key I actually use rndc.conf on my systems but I think the names and files are interchangeable. Dan Jul 8 20:39:37 ethic named[84090]: couldn't add command channel 127.0.0.1#953: file not found Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel :: 1#953: file not found Jul 8 20:39:37 ethic named[84090]: the working directory is not writable Jul 8 20:39:37 ethic named[84090]: running This, after I added your named_flags line into /etc/rc.conf. Where I get lost is *what* gives me that none:0 lines?? I see the same or worse err when I drop in bind98. IIRC, named does run, but the messages log is fulll of rndc.key error messages that I just cannot understand. _Now_, having dropped in your named_flags line, I am seeing something similar. I haved grepped thru the entire /etc/ tree and haven't found anything that explains where I messed up Ideas? thanks to you or anybody else onlist. gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Sat, Jul 09, 2011 at 07:49:43AM -0600, Dan Busarow wrote: Date: Sat, 9 Jul 2011 07:49:43 -0600 From: Dan Busarow d...@buildingonline.com Subject: Re: DNS and file system messed up... To: Gary Kline kl...@thought.org Cc: freebsd-questions@freebsd.org, Gary Kline kl...@magnesium.net X-Mailer: Apple Mail (2.753.1) On Jul 8, 2011, at 9:54 PM, Gary Kline wrote: On Fri, Jul 08, 2011 at 07:27:12AM -0600, Dan Busarow wrote: Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan Dan! I think you fixed something. I haven't figured this out yet, and would be grateful if you could decode this in /var/log/messages:: Jul 8 20:39:32 ethic named[83003]: stopping command channel on ::1#953 Jul 8 20:39:32 ethic named[83003]: exiting Jul 8 20:39:37 ethic named[84090]: starting BIND 9.3.6-P1 -c /etc/namedb/named.conf -t /var/named -u bind Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Gary, Theres probably an /etc/rc.conf line to fix these but what I always do is simply symlink /etc/namedb/rndc.key to /etc/rndc.key # ln -s /etc/namedb/rndc.key /etc/rndc.key I actually use rndc.conf on my systems but I think the names and files are interchangeable. Dan No joy. I just tried that from /etc: lrwxr-xr-x 1 root wheel21 Jul 9 11:18 namedb - /var/named/etc/namedb lrwxr-xr-x 1 root wheel20 Jul 9 11:17 rndc.key - /etc/namedb/rndc.key and I find the same warnings/complainnts as earlier. The good news, still, is that bin9 works. But I still get a lookup error from the -questions list in /var/log/maillog, so nothing is getting thru to the list from here at thought.org. FWIW: Yesterday, I got the latest 7.3 upgrade and compiled it. I habe NOT yet installed anything new because the last thing i want to do is lose my own link with the real world . :-) * 0.5 your thoughts what I should try next, please? gary Jul 8 20:39:37 ethic named[84090]: couldn't add command channel 127.0.0.1#953: file not found Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel ::1#953: file not found Jul 8 20:39:37 ethic named[84090]: the working directory is not writable Jul 8 20:39:37 ethic named[84090]: running This, after I added your named_flags line into /etc/rc.conf. Where I get lost is *what* gives me that none:0 lines?? I see the same or worse err when I drop in bind98. IIRC, named does run, but the messages log is fulll of rndc.key error messages that I just cannot understand. _Now_, having dropped in your named_flags line, I am seeing something similar. I haved grepped thru the entire /etc/ tree and haven't found anything that explains where I messed up Ideas? thanks to you or anybody else onlist. gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Sat, Jul 09, 2011 at 09:14:21AM +0100, Matthew Seaman wrote:
Date: Sat, 09 Jul 2011 09:14:21 +0100
From: Matthew Seaman m.sea...@infracaninophile.co.uk
Subject: Re: DNS and file system messed up...
To: Gary Kline kl...@thought.org
CC: freebsd-questions@freebsd.org
On 08/07/2011 23:04, Gary Kline wrote:
On Fri, Jul 08, 2011 at 10:01:45AM +0100, Matthew Seaman wrote:
Date: Fri, 08 Jul 2011 10:01:45 +0100
From: Matthew Seaman m.sea...@infracaninophile.co.uk
Subject: Re: DNS and file system messed up...
To: freebsd-questions@freebsd.org
On 08/07/2011 08:25, Doug Hardie wrote:
On 7 July 2011, at 22:58, Gary Kline wrote:
Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf:
file not found
Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c
/var/named/etc/namedb/named.conf
The first one that fails is looking for /etc/named.conf. The second
one shows its in /var/named/etc/named/named.conf
Those are different locations. I suspect you have named_flags setup
in rc.conf pointing to /etc/namedb/named.conf rather than the right
location. Its also possible that its not set in rc.conf but defaults
in either the rc script or /etc/rc.d/named. On my system it appears
to default in /etc/rc.d/named.
FreeBSD defaults to running named chrooted. /etc/namedb is actually a
symbolic link:
hi matthew,
i found an in-depth post you wrote re mtree yesterday ( 07july ),
but i figured it was over my head in resetting anything i might need
to reset. i was going to write you offlist. decided to ask the
entire list.
% ls -la /etc/namedb
lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ -
/var/named/etc/namedb
so the files referenced are in fact exactly the same file. However, the
flags from the log extract don't look like the defaults to me. (I'm
running the dns/bind98 port, and the equivalent info from the log line
is '-t /var/named -u bind')
i was using bind98 rather than the earlier bind9 which is out of
date. but bind98 gave me troubles with the rndc.key and other, so i
chose to go back with what worked. --first thing is to get this
working with the older bind9. FWIW, both bind9's given me the same
error and failure. i have walked thru the named script to the point
where it creates the symlink. regardless, i cannot understand the
error and failure messages. i only know that my kill -9 and my
initialization by hand work.
Gary, what named related settings do you have in /etc/rc.conf? You
almost certainly don't need anything more than:
named_enable=YES
and perhaps
syslogd_flags=-ss -l /var/named/var/run/log
so named can log to the system syslog.
Hmmm [c]. as you may have seen in my post to Doug H. i only have
--
named_enable=YES
named_program=/usr/local/sbin/named
named_pidfile=/var/run/named/pid
OK. The good news is that the configuration that works for the system
built-in version of named will work for the dns/bind98 port with very
minor changes, if any.
First: where everything should live
/etc/namedb/named.conf --- named's config file
/etc/namedb/master --- zone files this server is master for
/etc/namedb/slave --- zone files this server slaves from
another master (rw by named)
/etc/named/working --- named's working directory (rw by named)
/etc/rndc.conf --- config file for rndc
There are various other files and directories under /etc/namedb which
you may or may not need depending on how you configure named; in any
case, just leave them in their default locations and with the
permissions the system gives them. (You can use mtree(8) to fix them up
if necessary -- but that's a whole other posting)
Now, although named defaults to running chrooted into /var/namedb, you
don't need to mention that path explicitly anywhere in the config. In
fact, you should think about the configuration as if there was no
chrooting happening at all.
Second: rc.conf settings
named_enable=YES
syslogd_flags=-ss -l /var/named/var/run/log
should be all you need to use the built-in version of named.
Third: rndc configuration
Generate a new rndc key and a config file by:
# rndc-confgen /etc/named/rndc.conf
This should create a new file /etc/namedb/rndc.conf preconfigured to
work with the named instance on the localhost. Look at the text of
the file -- commented out there's a chunk of stuff to copy into
named.conf So let's do that.
If the file contains:
# key rndc-key {
# algorithm hmac-md5;
# secret 0ABCDE123+45+67890==;
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { rndc-key; };
# };
Then copy that without the '#' quotes into named.conf In fact, I find
it helps to add a control for access to ::1 as well. So add this text
to /etc/namedb
Re: DNS and file system messed up...
On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: DNS and file system messed up...
On Jul 8, 2011, at 3:01 AM, Matthew Seaman wrote: On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/ named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c / var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. Actually /etc/named.conf is NOT the same as /etc/namedb/named.conf ergo it is not the same as /var/named/etc/ namedb/named.conf Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Fri, Jul 08, 2011 at 12:25:34AM -0700, Doug Hardie wrote: Date: Fri, 8 Jul 2011 00:25:34 -0700 From: Doug Hardie bc...@lafn.org Subject: Re: DNS and file system messed up... To: Gary Kline kl...@thought.org Cc: FreeBSD Mailing List freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1084) On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. Hm.. i understand most of this. grep -r from /etc found something i've never uderstood. chroot stuff. to me, root is always / and root's home is /rrot. I've never dug deeper. here is the named stuff in /etc/defaults dir: named_enable=NO # Run named, the DNS server (or NO). named_program=/usr/sbin/named # Path to named, if you want a different one. #named_flags=-c /etc/namedb/named.conf # Uncomment for named not in /usr/sbin named_pidfile=/var/run/named/pid # Must set this in named.conf as well named_uid=bind# User to run named as named_chrootdir=/var/named# Chroot directory (or not to auto-chroot it) named_chroot_autoupdate=YES # Automatically install/update chrooted # components of named. See /etc/rc.d/named. named_symlink_enable=YES # Symlink the chrooted pid file in my /etc/rc.conf file are the 3 named lines: named_enable=YES named_program=/usr/local/sbin/named named_pidfile=/var/run/named/pid I dont see anything here that could be messing me up unless by using the default lines, something is going waaay South. Lastly, has the /etc/rc.d/named script changed in the past year or two? thankee -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Fri, Jul 08, 2011 at 10:01:45AM +0100, Matthew Seaman wrote: Date: Fri, 08 Jul 2011 10:01:45 +0100 From: Matthew Seaman m.sea...@infracaninophile.co.uk Subject: Re: DNS and file system messed up... To: freebsd-questions@freebsd.org On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: hi matthew, i found an in-depth post you wrote re mtree yesterday ( 07july ), but i figured it was over my head in resetting anything i might need to reset. i was going to write you offlist. decided to ask the entire list. % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') i was using bind98 rather than the earlier bind9 which is out of date. but bind98 gave me troubles with the rndc.key and other, so i chose to go back with what worked. --first thing is to get this working with the older bind9. FWIW, both bind9's given me the same error and failure. i have walked thru the named script to the point where it creates the symlink. regardless, i cannot understand the error and failure messages. i only know that my kill -9 and my initialization by hand work. Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Hmmm [c]. as you may have seen in my post to Doug H. i only have -- named_enable=YES named_program=/usr/local/sbin/named named_pidfile=/var/run/named/pid Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Fri, Jul 08, 2011 at 07:27:12AM -0600, Dan Busarow wrote: Date: Fri, 8 Jul 2011 07:27:12 -0600 From: Dan Busarow d...@buildingonline.com Subject: Re: DNS and file system messed up... To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.753.1) On Jul 8, 2011, at 3:01 AM, Matthew Seaman wrote: On 08/07/2011 08:25, Doug Hardie wrote: On 7 July 2011, at 22:58, Gary Kline wrote: Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf The first one that fails is looking for /etc/named.conf. The second one shows its in /var/named/etc/named/named.conf Those are different locations. I suspect you have named_flags setup in rc.conf pointing to /etc/namedb/named.conf rather than the right location. Its also possible that its not set in rc.conf but defaults in either the rc script or /etc/rc.d/named. On my system it appears to default in /etc/rc.d/named. FreeBSD defaults to running named chrooted. /etc/namedb is actually a symbolic link: % ls -la /etc/namedb lrwxr-xr-x 1 root wheel 21 Jul 6 06:24 /etc/namedb@ - /var/named/etc/namedb so the files referenced are in fact exactly the same file. Actually /etc/named.conf is NOT the same as /etc/namedb/named.conf ergo it is not the same as /var/named/etc/namedb/named.conf Gary, add named_flags=-c /etc/namedb/named.conf to /etc/rc.conf. Or change /etc/namedb/named.conf to the /var version if you like/there is no symlink. Dan Dan! I think you fixed something. I haven't figured this out yet, and would be grateful if you could decode this in /var/log/messages:: Jul 8 20:39:32 ethic named[83003]: stopping command channel on ::1#953 Jul 8 20:39:32 ethic named[83003]: exiting Jul 8 20:39:37 ethic named[84090]: starting BIND 9.3.6-P1 -c /etc/namedb/named.conf -t /var/named -u bind Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel 127.0.0.1#953: file not found Jul 8 20:39:37 ethic named[84090]: none:0: open: /etc/rndc.key: file not found Jul 8 20:39:37 ethic named[84090]: couldn't add command channel ::1#953: file not found Jul 8 20:39:37 ethic named[84090]: the working directory is not writable Jul 8 20:39:37 ethic named[84090]: running This, after I added your named_flags line into /etc/rc.conf. Where I get lost is *what* gives me that none:0 lines?? I see the same or worse err when I drop in bind98. IIRC, named does run, but the messages log is fulll of rndc.key error messages that I just cannot understand. _Now_, having dropped in your named_flags line, I am seeing something similar. I haved grepped thru the entire /etc/ tree and haven't found anything that explains where I messed up Ideas? thanks to you or anybody else onlist. gary However, the flags from the log extract don't look like the defaults to me. (I'm running the dns/bind98 port, and the equivalent info from the log line is '-t /var/named -u bind') Gary, what named related settings do you have in /etc/rc.conf? You almost certainly don't need anything more than: named_enable=YES and perhaps syslogd_flags=-ss -l /var/named/var/run/log so named can log to the system syslog. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DNS and file system messed up...
On Thu, Jul 07, 2011 at 06:00:42PM +, Gary Kline wrote: Date: Thu, 7 Jul 2011 18:00:42 + From: Gary Kline kl...@magnesium.net Subject: DNS and file system messed up... To: FreeBSD Mailing List freebsd-questions@FreeBSD.ORG Guys, I'd be much obliged to learn why /etc/rc.named start fails. This has been going on for months. For some reason freebsd.org doesn't recognize part of my domain, so I'm writing from my backup site, magnesium net. I did *somrthing* that keeps /etc/rc.d/named from working correctly. On the second line below the ^+, you'll see a none:0:/etc/named.conf from messages. The only way I can exec bind9 is by first doing a kill -9, then explicitly starting named and then, with the -c switch , aiming it at my *real* named.conf. I don't want to finish my new/latest install of 7.3 until I understand this screwup. Nobody has any clues to the capture output? I'm surprised. -g # sh /etc/rc.d/named start Starting named. + # tail /var/log/messages Jul 7 10:16:33 ethic named[54366]: starting BIND 9.3.6-P1 -t /var/named -u bind Jul 7 10:16:33 ethic named[54366]: none:0: open: /etc/named.conf: file not found Jul 7 10:16:33 ethic named[54366]: loading configuration: file not found Jul 7 10:16:33 ethic named[54366]: exiting (due to fatal error) # tail /var/log/messages # kill -9 `head -1 /var/run/named/pid` # /usr/local/sbin/named -c /var/named/etc/namedb/named.conf Jul 7 10:17:56 ethic named[54371]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jul 7 10:17:56 ethic named[54371]: command channel listening on 127.0.0.1#953 Jul 7 10:17:56 ethic named[54371]: command channel listening on ::1#953 Jul 7 10:17:56 ethic named[54371]: running + -- Gary Kline Seattle BSD Users' Group (seabug) | kl...@magnesium.net Thought Unlimited Org's Alternate Email Site http://www.magnesium.net/~kline To live is not a necessity; but to live honorably...is a necessity. -Kant -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
