Re: Bind 9.3.0 on FreeBSD 5.2.1

2004-09-27 Thread Gordon Freeman
Try using rndc -s status In Bind9 all controls have been turned over to the r/ndc system. On Thu, 23 Sep 2004 02:04:30 -0500, Kyle S. Allender <[EMAIL PROTECTED]> wrote: > Hello. > > This is potentially a stupid question, but is there a known issue with the > rc script which controls named unde

Re: Bind 9.3.0 on FreeBSD 5.2.1 followup

2004-09-23 Thread kallender
I performed a pkg_delete of bind9, then did a clean install of bind 9.3.0 (final release) from source on the 5.2.1 machine. On reboot, I get these messages on console: login: Sep 23 10:44:00 bsd named[506]: could not listen on UDP socket: permission denied Sep 23 10:44:00 bsd named[506]: creating

Bind 9.3.0 on FreeBSD 5.2.1

2004-09-23 Thread Kyle S. Allender
Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named

Re: Bind 9.3.0 on FreeBSD 5.2.1

2004-09-23 Thread kallender
I installed Bind 9.3.0 on the machine using the information on this page: http://ezine.daemonnews.org/200303/bind9.html to completely replace the binary that is in the base OS install. It looks like there's a problem with the location of some of the installed pieces (support tools) of Bind 9.3.0

Bind 9.3.0 on FreeBSD 5.2.1

2004-09-23 Thread Robert Huff
[EMAIL PROTECTED] writes: > This is potentially a stupid question, but is there a known issue > with the rc script which controls named under FreeBSD 5.2.1? I think you are looking for something which doesn't exist. The only script involved with "controlling" named (that I know

Bind 9.3.0 on FreeBSD 5.2.1 startup problem

2004-09-23 Thread kallender
Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named

Bind 9.3.0 on FreeBSD 5.2.1

2004-09-23 Thread kallender
Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named