Caching nameserver only?

[Treptow, Craig]

nslookup requires an entry for the nameserver itself, which you apparently don't have.  Try adding records for 192.168.1.1 and retrying.  Alternatively, try your queries with dig and/or host.  They should work a little better than nslookup.

Craig

-----Original Message-----
From: marius at flage.nu [mailto:marius at flage.nu]
Sent: Tuesday, July 31, 2001 9:43 AM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: Caching nameserver only?



Hi there

I'm trying to set up a local nameserver. I want it to run as a
nameserver for my local network, and as a caching nameserver. I
thought that I should do this in two steps, and first get the caching
bit up and running.

I've set up the /etc/named.conf in the following way:

root at proxy:~# cat /etc/named.conf
// generated by named-bootconf.pl

options {
        directory "/var/named";
	listen-on { 192.168.1.1; 127.0.0.1; };
        /*
         * If there is a firewall between you and nameservers you want
         * to talk to, you might need to uncomment the query-source
         * directive below.  Previous versions of BIND always asked
         * questions using port 53, but BIND 8.1 uses an unprivileged
         * port by default.
         */
        // query-source address * port 53;
};

//
// a caching only nameserver config
//
//

zone "." IN {
        type hint;
        file "named.ca";
};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };
};

Then started the daemon with 'ndc start', and the following comes into
my /var/log/messages:

Jul 31 16:20:10 proxy named[181]: starting.  named 8.2.2-P5 Sat Nov 27
13:52:39 CST 1999 ^Iroot at blackhole:/tmp/bind-8.2.2-P5/src/bin/named
Jul 31 16:20:11 proxy named[181]: hint zone "" (IN) loaded (serial 0)
Jul 31 16:20:11 proxy named[181]: master zone "localhost" (IN) loaded
(serial 42)
Jul 31 16:20:11 proxy named[181]: master zone "0.0.127.in-addr.arpa"
(IN) loaded (serial 1997022700)
Jul 31 16:20:12 proxy named[181]: listening on [127.0.0.1].53 (lo)
Jul 31 16:20:12 proxy named[181]: listening on [192.168.1.1].53 (eth0)
Jul 31 16:20:12 proxy named[181]: Forwarding source address is
[0.0.0.0].1024
Jul 31 16:20:12 proxy named[182]: Ready to answer queries.

So, it seems to be starting alright.

Then for some lookups:

root at proxy:~# nslookup pat.uio.no 192.168.1.1
*** Can't find server name for address 192.168.1.1: No response from
server
*** Default servers are not available

root at proxy:~# nslookup pat.uio.no localhost
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
Name:    pat.uio.no
Address:  129.240.130.16

And from a remote machine, on the same subnet as the dns:

marius at fugazi:~$ nslookup pat.uio.no 192.168.1.1
*** Can't find server name for address 192.168.1.1: No response from
server
*** Default servers are not available

So, I can feel that I'm poking at the core of the problem, but I can't
see how to fix it?

I was told that samba could force a dialup when trying to perform
lookups, so that's why I needed the caching nameserver to prevent that
from happening. Is this correct? And, secondly, I want the local
nameserver to get rid of some annoying timeouts on my LAN. Will that
solve it?

Anyone care to shed some light on these issues? Any help would be
greatly appreciated.

Marius