Selective forwarding for reverse zones?

[Treptow, Craig]

Ok, I seem to have other problems on this box.  Named didn't like "ndc trace",
nor will it respond to some other ndc commands.  So, I started named like
this:

/usr/local/sbin/named -d 1

Now named.run looks like this:

# head named.run
Debug level 1
Version = named 8.2.2-P5 Sun Jan 28 21:24:11 CST 2001
        root at fozzy:/usr/local/src/bind-8.2.2-p5/src/bin/named
conffile = /etc/named.conf
starting.  named 8.2.2-P5 Sun Jan 28 21:24:11 CST 2001
        root at fozzy:/usr/local/src/bind-8.2.2-p5/src/bin/named
ns_init(/etc/named.conf)
Adding 64 template zones
evSetTimer(ctx 0x20058378, func 0x20005c54, uap 0x20023380, due
985573608.857157
000, inter 0.000000000)
evSetTimer(ctx 0x20058378, func 0x20005c54, uap 0x200233b0, due
985573613.904002
000, inter 0.000000000)

This last line keeps repeating....

This must be correspond to the "STILL priming" from the status output:

# ndc status
named 8.2.2-P5 Sun Jan 28 21:24:11 CST 2001
root at fozzy:/usr/local/src/bind-8.2.
2-p5/src/bin/named
number of zones allocated: 64
debug level: 1
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is ON
server is STILL priming
server IS NOT loading its configuration

So when I try the lookup and look at named.run, I don't see anything but the
above repeated message.

This machine has no path to the Internet.  In its named.conf we have:

options {
        directory "/usr/local/named";
        pid-file "/etc/named.pid";
        named-xfer "/usr/local/bin/bind/named-xfer";
//      notify yes;
        notify no;
        check-names master ignore;              /* default. */
//      check-names slave  ignore;
//      datasize 20M;
//      files unlimited;
        listen-on port 53 { any; };
        forward only;
        forwarders {192.168.34.5;};
        allow-query { any; };
        allow-transfer { any; };
};

Plus a logging section and our local zones, and this one:

zone "." IN {
        type hint;
        file "db.cache";
};

I'm guessing that the priming never completes because this box can't
communicate to the outside world.  If so, what should we have for boxes in
this scenario?

Back to the original thread, if this "STILL priming" business isn't related to
the problem, once this is fixed, I can get the trace output.



-----Original Message-----
From: Barry Margolin [mailto:barmar at genuity.net]
Sent: Tuesday, April 11, 2000 1:19 PM
To: comp-protocols-dns-bind at moderators.isc.org
Subject: Re: Selective forwarding for reverse zones?


In article
<93D3D41C8EB4D2119C4200805F9F496107C33035 at pfgdsmmsg010.principal.com>,
Treptow, Craig <Treptow.Craig at principal.com> wrote:
>Is that the tracing you meant?  

No, I meant "ndc traceon".  This tells named to write everything it's doing
to the file named.run.

>I've had little exposure to the tracing/debug output, so if the answer is
>staring me in the face, please let me know.

Chapter 12 of the DNS&BIND book talks about understanding named's tracing
output.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the
group.