Forwarding and delegation
Mark_Andrews at iengines.com
Mark_Andrews at iengines.com
Mon Nov 1 04:15:28 UTC 1999
I seem to remember fixing something like this for 8.2.2. If you
still have a problem with 8.2.2 submit a bug report.
789. [bug] #669 was too aggressive. more than cached data was
removed.
Mark
> I tried this, but it still didn't work. Finally, I fugured out what was caus
> ing
> the problem, and it seems to be a bug in BIND. If I specify in named.conf fi
> rst
> the zone for the domain and then for sub-domain, the information for subdomai
> n is
> ignored. If I do it in reverse order, everything works fine. Here is exampl
> e:
>
> options {
> directory "/var/named";
> forwarders {
> XXXX;
> XXXX;
> };
> forward only;
> };
>
> zone "dev.morgan.com" {
> type forward;
> forwarders { };
> };
>
> zone "morgan.com" {
> type master;
> file "zone/morgan.com";
> };
>
>
> This works fine. However, if I switch the two zone definitions around, deleg
> ation
> for "dev.morgan.com" will stop working.
>
> Another point. BIND documentation for forward zone says "If either no forwa
> rders
> statement is present in the zone or an empty list for forwarders is given, th
> en no
> forwarding will be done for the zone, cancelling the effects of any forwarder
> s in
> the options statement. " Actually, this does not work without an empty forwa
> rders
> list (as Barry already pointed to me).
>
> Barry Margolin wrote:
>
> > In article <3818C345.A36D0351 at ms.com>, Sam Shteingart <samsh at ms.com> wrote
> :
> > >I want to use forwarding on my name server, plus delegation (via NS
> > >records) for some of the subdomains. I know that this didn't work in
> > >BIND 4.X.
> > >
> > >I now installed BIND 8.2.1 and tried to set this up, but it still
> > >doesn't work. I defined zones that I want to delegate to as forward
> > >zones:
> > >
> > >zone "subdomain" {
> > > type forward;
> > >}
> > >
> > >but this didn't do the trick. I also could not find an answer on
> > >several FAQ lists. Is there a way to implement this?
> >
> > zone "subdomain" {
> > type forward;
> > forwarders { };
> > }
> >
> > The empty forwarders list in the zone overrides the general forwarders
> > list, and causes this zone *not* to use any forwarders, which means that it
> > reverts to the normal behavior of using NS records.
> >
> > Yes, it's kind of backwards. Suggestion to BIND developers: how about
> > creating "type no-forward", which implements this.
> >
> > --
> > Barry Margolin, barmar at bbnplanet.com
> > GTE Internetworking, Powered by BBN, 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 gr
> oup.
>
> --
> Sam Shteingart Morgan Stanley Dean Witter Co.
> Phone: (212) 762-2377 Fax: (212)762-1009
>
> e-mail: samsh at ms.com
>
>
>
>
>
--
Mark Andrews, Internet Engines Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at iengines.com
More information about the bind-users
mailing list