bind8 contacting forwarder on startup ?

[Kevin Darcy]

I don't think that'll help. It'll *still* want to prime the root-zone information,
and it'll use the forwarders to do that even if you have a hints file.

The only "solution" I've been able to come up for this "priming causes
dial-on-demand" problem is to have separate "connected" and
"disconnected" nameserver configurations, and to somehow script switching back and
forth between the two. But I've never actually tried this since I have no
dial-on-demand capability.


- Kevin

Michael Kjorling wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> This seems to be something of a FAQ. BIND wants to contact the root
> servers so it knows where to go - I'm fairly sure this is what you are
> seeing even though you're forwarding. Grab the hints file and put in a
> zone "." { type hint; ... }; into your named.conf and you should be
> OK.
>
> Michael Kjörling
>
> On Jun 22 2001 01:36 -0700, Ben Z. Peridol wrote:
>
> > Hi folks,
> >
> > I have set up a linx box for a small office network for dial-in (isdn),
> > firewalling, and everything. On that box I installed bind8 for resolving our
> > internal host addresses (10.x.x.x). Since I want to resolve all external
> > addresses by way of my isp's dns, I have no zone "." { type hint; } but added
> > a forward only; forwarders { 195.182.96.28; }; with 195.182.96.28 being the
> > dns-server of our isp. This all works fine, but what is pretty annoying is that
> > bind wants to contact the forwarder everytime it starts up. Since it's an auto-
> > dial-on-demand setup I want to minimize traffic on the line, so I'm wondering
> > if there is a way of  how I can tell bind not trying to talk to the forwader
> > except for resolving external addresses.
> > (Also tried forward first; but didn't change anything)
> >
> > thanks for hints,
> >
> > Ben
>
>