Date: Tue, 3 Dec 2002 16:57:23 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-stable@FreeBSD.ORG Subject: Re: Named problem Message-ID: <20021203165723.GB74738@happy-idiot-talk.infracaninophi> In-Reply-To: <20021203172500.GA23429@dasboot.birch.se> References: <20021203172500.GA23429@dasboot.birch.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 03, 2002 at 05:25:00PM +0000, User Thrawn wrote:
> Im having some problems to get named/bind working correctly. I can only resolve 127.0.0.1 and other domains/ip addresses that im not master for.
> Im using bind9 from ports, Im using version 9.2.1.
>
> When i try to resolv localhost it says:
>
> > localhost
> Server: localhost
> Address: 127.0.0.1
>
> *** localhost can't find localhost: Non-existent host/domain
> >
>
> I start named from /etc/namedb/master/usr/sbin, with the command:
Hmmm... With the bind-9.2.1 port, you don't need to install everything
under the chroot directory, neither do you need to either staticly
link the programs or copy any shlibs under the the chroot.
> named -c /etc/namedb/named.conf -t /etc/namedb/master -u bind and then I get this in messages:
>
> Dec 3 17:01:18 dasboot named[23499]: starting BIND 9.2.1 -c /etc/namedb/named.conf -t /etc/namedb/master -u bind
> Dec 3 17:01:18 dasboot named[23499]: command channel listening on 127.0.0.1#953
> Dec 3 17:01:18 dasboot named[23499]: command channel listening on ::1#953
Right --- do you have:
syslogd_flags="-ss -l /etc/namedb/master/var/run/log"
so you can see any log messages produced after named calls chroot(2)?
> host { any; } {
> topology {
> 127.0.0.0/8 192.168.0.0/24;
> };
> };
Hmmmm.. According to
file:///usr/local/share/doc/bind9/arm/Bv9ARM.ch06.html#Configuration_File_Grammar
there isn't any mention of such a thing as a 'host' top level block in
the config file. There's a 'topology {};' element that is part of the
'options {};' block. However, it defaults to: 'topology { localhost;
localnets; };' which is pretty much what you have already.
> zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" {
> type master;
> file "localhost-v6.rev";
> allow-query { 127.0.0.1/32; 192.168.0.0/24;
> };
> };
The 1.0....0.IP6.INT zone (RFC 1886) is deprecated now. You should also use:
zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" {
type master;
file "localhost-v6.rev";
allow-query { 127.0.0.1/32; 192.168.0.0/24;
};
};
which is from RFC 3152, and seeing as you're running bind-9.2.1, you
might use bitstring labels as well:
zone "\[x00000000000000000000000000000001].IP6.ARPA" {
type master;
file "localhost-v6.rev";
allow-query { 127.0.0.1/32; 192.168.0.0/24;
};
};
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021203165723.GB74738>