Caching only server problem.

[Kevin Darcy]

Since you're on a 10.*.*.* network, I assume you're using some form of
forwarding to be able to resolve those registered addresses. And I assume
further that you are *not* using your master as your general forwarder,
otherwise you'd be able to resolve whatever the master could resolve. Given
those assumptions, you need to set up the apex zones -- e.g.
"example.com" and/or "10.in-addr.arpa", but not any children such as
"foo.example.com" or "0.10.in-addr.arpa" -- of all your internal domains
(forward and/or reverse) on your nameserver as zones of type "slave",
"stub" or "forward". Note that if you choose "slave" or "stub", you may need
to specify "forwarders { }" in the zone definition in order to cancel
forwarding for any subzones.

I could go into more detail as to the tradeoffs between "slave", "stub" and
"forward", if you'd like. Or just search the archives. I've discussed this
many times before.


- Kevin

sworden at focal.com wrote:

> I'm running BIND 8.2.3 on a non registered 10.x.x.x network.  All my
> servers are running Solaris 2.6 or 7.  I have a master server that is setup
> and working properly, identifying all IP's registered and my internals.
> I'm trying to setup a caching only server.  I have my resolv.conf file
> pointing to 127.0.0.1.  My named.conf file has a 0.0.127.in-addr.arpa and .
> zones.  My db.cache file I downloaded from the web.  I can lookup and
> registered address, but non of the addresses on my master.  Can anyone
> help?
>
> Stephen Worden
> BNE NMS Engineer
> Focal Communications
> Tel: 847-954-8306
> Fax: 847-954-7710
> Email: sworden at focal.com