On Tue, Dec 03, 2002 at 11:03:19PM +0000, Matthew Seaman wrote:
> I wrote some notes about configuring Bind9 chroot'ed that I sent to
> the [EMAIL PROTECTED] list --- a bit sketchy I'm afraid,
> but it's at:
>
>
>http://listserver.uk.freebsd.org/pipermail/freebsd-users/2002-November/006883.html
>
> if you're interested.
Well if I don't get named working I don't have any choice do I? :P
> It's a unix domain socket, as it should be. That's what the 's' in
> 'srw-rw-rw-' means. Now when you restart named(8) you should see some
> more meaningful error messages in /var/log/messages or
> /var/log/all.log (if you've enabled it --- see
> /etc/syslog.conf). Bind9 is a lot pickier about the config file and
> zone file syntax than Bind8, so you've probably got some debugging to
> do. Ultimately, once you've fixed all the show stoppers, you
> should see the "Ready to answer queries." message that indicates
> everything is working OK.
Aha okej, I was just wondering if it hade the right permission I thought it was to be
a regular log file but syslog is using it to forward the info to /var/log/messges or
/var/log/all.log if I understand it right now.
> > > > host { any; } {
> > > > topology {
> > > > 127.0.0.0/8 192.168.0.0/24;
> > > > };
> > > > };
Well I commeted out this above with hash.
> > > 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.
> >
> > So you are saying that I should remove it then?
See above.
Any how this is what my all.log says about named when I start it:
Dec 4 16:48:37 dasboot named[5704]: starting BIND 9.2.1 -c /etc/namedb/named.conf -t
/etc/namedb/master -u bind
Dec 4 16:48:37 dasboot named[5704]: using 1 CPU
Dec 4 16:48:37 dasboot named[5704]: loading configuration from
'/etc/namedb/named.conf'
Dec 4 16:48:37 dasboot named[5704]: listening on IPv4 interface xl0, 192.168.0.1#53
Dec 4 16:48:37 dasboot named[5704]: listening on IPv4 interface lo0, 127.0.0.1#53
Dec 4 16:48:37 dasboot named[5704]: listening on IPv4 interface tun0, 62.66.14.24#53
Dec 4 16:48:37 dasboot named[5704]: command channel listening on 127.0.0.1#953
Dec 4 16:48:37 dasboot named[5704]: command channel listening on ::1#953
Dec 4 16:48:37 dasboot named[5704]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial
20021128
Dec 4 16:48:37 dasboot named[5704]: zone
\[x00000000000000000000000000000001/128].IP6.ARPA/IN: loaded serial 20021128
Dec 4 16:48:37 dasboot named[5704]: running
--------------EOF---------------
And this is what it says in my messages:
Dec 4 16:48:37 dasboot named[5704]: starting BIND 9.2.1 -c /etc/namedb/named.conf -t
/etc/namedb/master -u bind
Dec 4 16:48:37 dasboot named[5704]: command channel listening on 127.0.0.1#953
Dec 4 16:48:37 dasboot named[5704]: command channel listening on ::1#953
--------------EOF---------------
One thing I find strange is that it starts to listen on xl0 ( 192.168.0.1 ) but when I
specify 192.168.0.1 as my nameserver in resolv.conf i get this error message:
dasboot/usr/home/thrawn: nslookup 4:51PM
*** Can't find server name for address 192.168.0.1: Server failed
*** Default servers are not available
dasboot/usr/home/thrawn:
And my resolv.conf looks like this:
domain birch.se
#nameserver 127.0.0.1
nameserver 192.168.0.1
#nameserver 212.242.40.2
search birch.se
---------EOF------------
But starting using 127.0.0.1 as my nameserver do work but It can't resolv the names
etc that I have in my own domain. And that I can't understand why its so. As i said
earlyer the only name that my domain server can resolv is 127.0.0.1 but localhost does
not work. And any other domain name etc that I have in my config files it can't resolv
but none local it can.
> Yes. See if commenting it out makes your nameserver behave better.
Well I don't see any diffrence yet.
And thanks for the help so far.
Mvh Mattias Bj�rk
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
