I'm going to answer my own post here...

I removed the entry from /etc/rc.conf and instead put an entry in
/etc/rc.local (had to create that file).  Now named starts up properly on
restart of the system.

I am now able to use rndc as expected to control the daemon - thanks to Mr.
Huff pointing out the expected location being different than what was
installed.

I'm not horribly concerned about this now that I've got it working, but I'm
still a little confused as to how the rcNG functions.  I found a paper on it
here:

http://www.usenix.org/events/usenix01/freenix01/full_papers/mewburn/mewburn_
html/index.html

for those that are interested.

I'm looking for more information and tutorials on it - I'll keep working
with it, but pointers would be appreciated.

Anyway, again I extend my thanks to Robert.

Cheers,

Kyle


On 23/09/2004 12:12, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> rambled:

> Hello again.
> 
> I'm still stumped.  I thought that perhaps something had gone wrong during the
> install initially.  I performed a clean install without named or Linux
> compatibility being enabled.
> 
> I then used the references on this page:
> 
> http://ezine.daemonnews.org/200303/bind9.html
> 
> to build a clean copy of Bind9.3.0 over the top of the base distribution that
> ships with FBSD 5.2.1.
> 
> It will start manually from the CLI with either:
> 
> named
> /usr/sbin/named
> 
> and properly read the zones and configuration files, inclusive of rndc-key.
> 
> However, I still can't control named via /etc/rc.d/named and on startup the
> system spits out several errors with regards to named and being unable to open
> interfaces.  It's as if networking isn't up yet, so named can't start.  But if
> networking were not running, I wouldn't see errors about addresses and
> interfaces already being in use.
> 
> I did make one change to /etc/rc.conf, adding this line at the end:
> 
> /usr/sbin/named
> 
> The messages log looks like this:
> 
> Sep 23 12:00:00 bsd named[472]: starting BIND 9.3.0
> Sep 23 12:00:00 bsd named[472]: could not listen on UDP socket: permission
> denied
> Sep 23 12:00:00 bsd named[472]: creating IPv4 interface de0 failed; interface
> ignored
> Sep 23 12:00:00 bsd named[472]: could not listen on UDP socket: permission
> denied
> Sep 23 12:00:00 bsd named[472]: creating IPv4 interface lo0 failed; interface
> ignored
> Sep 23 12:00:00 bsd named[472]: not listening on any interfaces
> Sep 23 12:00:00 bsd named[472]: /etc/namedb/named.conf:28: couldn't add
> command
> channel 127.0.0.1#953: permission denied
> Sep 23 12:00:00 bsd named[472]: couldn't open pid file
> '/var/run/named/named.pid': File exists
> Sep 23 12:00:00 bsd named[472]: exiting (due to early fatal error)
> Sep 23 12:02:53 bsd login: ROOT LOGIN (root) ON ttyv0
> Sep 23 12:03:28 bsd named[184]: stopping command channel on 127.0.0.1#953
> Sep 23 12:03:28 bsd named[429]: exiting
> Sep 23 12:03:28 bsd named[184]: exiting
> Sep 23 12:03:34 bsd named[487]: starting BIND 9.3.0
> Sep 23 12:03:34 bsd named[487]: command channel listening on 127.0.0.1#953
> Sep 23 12:03:47 bsd login: ROOT LOGIN (root) ON ttyv0
> Sep 23 12:04:17 bsd named[499]: starting BIND 9.3.0
> Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use
> Sep 23 12:04:17 bsd named[499]: creating IPv4 interface de0 failed; interface
> ignored
> Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use
> Sep 23 12:04:17 bsd named[499]: creating IPv4 interface lo0 failed; interface
> ignored
> Sep 23 12:04:17 bsd named[499]: not listening on any interfaces
> Sep 23 12:04:17 bsd named[499]: /etc/namedb/named.conf:28: couldn't add
> command
> channel 127.0.0.1#953: address in use
> Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use
> Sep 23 12:04:17 bsd named[499]: creating IPv4 interface de0 failed; interface
> ignored
> Sep 23 12:04:17 bsd named[499]: could not listen on UDP socket: address in use
> Sep 23 12:04:17 bsd named[499]: creating IPv4 interface lo0 failed; interface
> ignored
> 
> Note that there is a named.pid file in /var/run/named after a reboot -
> possibly
> created by the system on boot?  Is the OS trying to start named too early?
> /etc/defaults/rc.d contains:
> 
> #
> # named.  It may be possible to run named in a sandbox, man security for
> # details.
> #
> named_rcng="NO"                 # XXX Temporary. Enable to use new rc
>                                 #    functionality in support of named. See
>                                 #    variables below.
> 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="-u bind -g bind"   # Flags for named
> named_pidfile="/var/run/named/pid" # Pid file
> named_chrootdir=""              # 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 ${named_pidfile} and /var/run/ndc
>                                 # to their chrooted counterparts.
> 
> 
> The /etc/rc.d/named script is unaltered from clean install of the OS.
> 
> I am _super_ confused here.  Can anyone help?
> 
> Kyle
> 
> _______________________________________________
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

-- 
 
Kyle Allender                           [EMAIL PROTECTED]
1574 195th St.                          [EMAIL PROTECTED]
Jefferson, IA 50129                     [EMAIL PROTECTED]
515.386.3516                            [EMAIL PROTECTED]
515.210.5027 cell



_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to