Newbie install help

[Kevin Darcy]

Mark_Andrews at iengines.com wrote:

> > You could also do this the old-fashioned way and become a slave for their zon
> > es,
> > but then you'd have to define not only the top level of their domain, but
> > *every* *one* of their zones on all of your servers (otherwise queries in
> > subzones will use the global forwarder), and this could become a maintenance
> > nightmare. This alternative might be mandatory if the only servers of the
> > "other" intranet you can reach have recursion turned off, or you might choose
> > this option for performance reasons. In terms of resource usage, the optimal
> > choice of forwarding versus being a slave is driven by a number of factors,
> > including frequency and variety of queries for the zone, size of the zone,
> > frequency of changes to the zone, TTL/refresh settings for the zone, and whet
> > her
> > IXFR is available.
>
>         Just add a empty forwarders clause to slave zone to disable
>         forwarding for the subzones.
>
>         e.g.
>                 options {
>                         forwarders { <IP ADDRESS LIST> };
>                 };
>
>                 zone "example" {
>                         type slave;
>                         masters { <IP ADDRESS LIST> };
>                         file "cache/example";
>                         // disable global forwarding for child zones
>                         forwarders { };
>                 };
>
>         Queries for foo.sub.example will follow the normal resolution
>         procedures.
>
>         The same procedure can be applied to stub and master zones
>         as well.
>

Oh, I didn't know you could have a forwarders directive for any zone that wasn't
"type forward". That's kinda neat.


- Kevin