forwarding problem - server failed

[bleve at my-deja.com]

I'm setting up a simple (for now) forwarding nameserver on an
internal box, that I want to forward all its queries to another DNS
server (and eventually use BIND 8.2.2's zone forwarding to use
multiple nameservers, but for now one will do).

I have the following named.conf file in /usr/local/etc/


{115} : m named.conf

// named.conf for fwlser01's DNS server
// BIND 8.x

// $Id: named.conf,v 1.6 1999/06/15 03:57:02 root Exp root $

options {
        pid-file "/etc/named.pid";
        forwarders {
                172.16.13.69;
        };
        forward only;
};


which should be ok. Using nslookup to test it shows this :

{116} : nslookup
Default Server:  unisysproxy-le1.interconnect
Address:  172.16.13.69

> admin04.interconnect
Server:  unisysproxy-le1.interconnect
Address:  172.16.13.69

Name:    admin04.interconnect
Address:  172.16.13.142

Good, /etc/resolv.conf works, the remote DNS server works ...


> server 127.0.0.1
Default Server:  localhost
Address:  127.0.0.1

> unisysproxy-le1.interconnect
Server:  localhost
Address:  127.0.0.1

*** localhost can't find unisysproxy-le1.interconnect: Server failed

Hmmmm.  That's not right.

Checking for errors in /var/adm/messages :


Nov 19 15:14:27 fwlser01 named[12589]: starting.  named 8.2.2-P5 Fri
Nov 19 14:09:43 EST 1999
Nov 19 15:14:27 fwlser01        foo at fwlser01:/tmp/bind-8.2.2-
p5/src/bin/named
Nov 19 15:14:27 fwlser01 named[12590]: Ready to answer queries.

hmm, nothing wrong there.

What's ndc saying about named's status?

{117} : ndc status
named 8.2.2-P5 Fri Nov 19 14:09:43 EST 1999  root at fwlser01:/tmp/bind-
8.2.2-p5/src/bin/named
number of zones allocated: 64
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
server is STILL priming
server IS NOT loading its configuration
{118} :

the server is still priming is odd.

the only config I have at the moment for named is the named.conf file,
as I'm just trying to get it to be a caching forwarder (ie:
replicate the function of /etc/resolv.conf).  Later I want to point it
to multiple servers for different zones, but as above, I want to walk
it around before asking it to fly.

Any clues as to what I've done wrong?  AFAIK if I'm just forwarding
I shouldn't need any root.cache files or similar, the named.conf
above should be all I need.  Have I misunderstood?














Sent via Deja.com http://www.deja.com/
Before you buy.