Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Aug 2002 11:49:57 +0530
From:      "Unix Tools" <unixtools@hotmail.com>
To:        <thrawn@linux.nu>, <freebsd-questions@freebsd.org>
Cc:        <thrawn@thrawn.birch.se>
Subject:   Re: Named Problem
Message-ID:  <OE41YcDnpTYA6i447tT00018c66@hotmail.com>
References:  <20020819171821.GA35640@thrawn.birch.se>

next in thread | previous in thread | raw e-mail | index | archive | help
in /etc/namedb create a file named db.127.0.0

and in the named.conf
zone "0.0.127.IN-ADDR.ARPA" {
        type master;
        file "/etc/namedb/db.127.0.0";
};

----- Original Message -----
From: <thrawn@linux.nu>
To: <freebsd-questions@freebsd.org>
Cc: <thrawn@thrawn.birch.se>
Sent: Monday, August 19, 2002 10:48 PM
Subject: Named Problem


> Hi,
>
> I have installed bind9 ( from ports /usr/ports/net/bind9 ) And copied the
named binary to /var/named/usr/sbin.
> I start bind from /var/named/usr/sbin with the command:
>
> ./named -c /etc/named.conf -t /var/named -u bind
>
> The user bind is there in /etc/master.passwd:
>
> bind:*:53:53:Bind Sandbox:/:/sbin/nologin
>
> I have also runed ldd named, the output is:
>
> named:
>         libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x28181000)
>         libc.so.4 => /usr/lib/libc.so.4 (0x2823d000)
>
> I have put the libs in /var/named/usr/lib
>
> When I start bind I don't get any fatal errors, this is from my
/var/log/messges when I run ./named -c /etc/named.conf -t /var/named -u
bind:
>
> Aug 19 19:08:49 dasboot named[3814]: starting BIND 9.2.1 -c
/etc/named.conf -t /var/named -u bind
> Aug 19 19:08:49 dasboot named[3814]: none:0: open:
/usr/local/etc/rndc.key: file not found
> Aug 19 19:08:49 dasboot named[3814]: couldn't add command channel
127.0.0.1#953: file not found
> Aug 19 19:08:49 dasboot named[3814]: none:0: open:
/usr/local/etc/rndc.key: file not found
> Aug 19 19:08:49 dasboot named[3814]: couldn't add command channel ::1#953:
file not found
> Aug 19 19:08:49 dasboot named[3814]: localhost.rev:1: no TTL specified;
using SOA MINTTL instead
> Aug 19 19:08:49 dasboot named[3814]: zone 0.0.127.IN-ADDR.ARPA/IN: has no
NS records
> Aug 19 19:08:49 dasboot named[3814]: db.0.168.192:1: no TTL specified;
using SOA MINTTL instead
> Aug 19 19:08:49 dasboot named[3814]: zone 0.168.192.in-addr.arpa/IN: has
no NS records
> Aug 19 19:08:49 dasboot named[3814]: localhost.rev:1: no TTL specified;
using SOA MINTTL instead
> Aug 19 19:08:49 dasboot named[3814]: zone
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/IN:
has no NS records
> Aug 19 19:08:49 dasboot named[3814]: db.birch.se:1: no TTL specified;
using SOA MINTTL instead
>
> ps auxc | grep named displays the following:
>
> bind    3814  0.0  0.4  3196 2280  ??  Ss    7:08PM   0:00.04 named
>
> And I can't see any fatal messages, this is the output of sockstat | grep
53
>
> bind     named     3814    7 udp4   192.168.0.1:53        *:*
> bind     named     3814    8 tcp4   192.168.0.1:53        *:*
> bind     named     3814    9 udp4   127.0.0.1:53          *:*
> bind     named     3814   10 tcp4   127.0.0.1:53          *:*
> bind     named     3814   11 udp4   62.66.14.12:53        *:*
> bind     named     3814   12 tcp4   62.66.14.12:53        *:*
> bind     named     3814   13 udp4   *:53                  *:*
>
> As you can see its listining to the port 53 on all interfaces. I also have
a firewall and my rules are for the moment when I try to get this working:
>
> 00100 allow tcp from any to any
> 00200 allow udp from any to any
> 65535 allow ip from any to any
>
> When I run nslookup I get this error:
>
> *** Can't find server name for address 127.0.0.1: Server failed
> *** Can't find server name for address 192.168.0.1: Server failed
>
> My /etc/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
>
> Note that birch.se is only an internal domain in my dns server it does not
excisit on the internet.
>
> and the ip addresses are correct, this is the output of ifconfig xl0:
>
> xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         options=3<rxcsum,txcsum>
>         inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
>         inet6 fe80::2a0:24ff:fe53:cc3a%xl0 prefixlen 64 scopeid 0x1
>         ether 00:a0:24:53:cc:3a
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
>
> I have supplyed as mutch information as I can think of. If Im missing
something please let me know. I don't get it why it shoulden't work. I have
tested nslookup with port=53 option but does not help, still the same error
message.
> Any thoughts are welcome. It might be a silly misstake Im doing here but I
have no clue of what that could be.
>
> Mvh Mattias Björk
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?OE41YcDnpTYA6i447tT00018c66>