delegating NS control of subdomain to another BIND

[Kevin Darcy]

Did you try adding "forwarders { }" to the madduck.net zone definition?


- Kevin

Martin F. Krafft wrote:

> also sprach Kevin Darcy (on Mon, 23 Jul 2001 05:01:07PM -0400):
> > Well, according to the dump, pns.dtag.de (address 194.25.0.125) is the one
> > disclaiming all knowledge of mail.subdomain.madduck.net. You haven't
> > mentioned forwarding at all, but since pns.dtag.de has nothing to do with
> > the madduck.net domain, I can only conlude that you're using pns.dtag.de as
> > a forwarder. Is that correct? If you're forwarding, then you'll have to use
> > the "forwarders { }" syntax in the zone definition of madduck.net if you
> > want to cancel forwarding for its subzones.
>
> well, first it's not called subdomain.madduck.net :)
> and then, currently, this is a merely internal test. none of my
> forwarders, of which pns.dtag.de is one, knows about
> subdomain.madduck.net. note the 192.168.14.0/24 subnet choice.
>
> all this is within my private lan. i have three dns servers, two only
> for the purpose of testing. they all run bind 9.1.3.
>
>   192.168.14.1 is the main dns server, which does recursion - all my
>     lan resolves through it. it is authoritative for home.madduck.net
>     on 192.168.14.0/24 only, and forwards everything else to some
>     eight dtag.de servers. it has an NS record for
>     subdomain.home.madduck.net pointing to ns{1,2}.subdomain... and
>     contains A (glue) records for ns{1,2}.subdomain... to
>     192.168.14.1{3,4}.
>
>   192.168.14.1{3,4} are two test servers authoritative for
>     subdomain.home.madduck.net.
>
> however, while queries to e.g. mail.subdomain.home.madduck.net against
> 192.168.14.1{3,4} resolve just fine to 192.168.14.7, the same queries
> fail with NXDOMAIN when placed against 192.168.14.1. that's my problem
> and even though i did everything you have to do, nothing works.