delegating NS control of subdomain to another BIND

[Kevin Darcy]

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.


- Kevin

Martin F. Krafft wrote:

> also sprach Kevin Darcy (on Fri, 20 Jul 2001 08:31:04PM -0400):
> > By "doesn't work", you mean you're still getting NXDOMAIN answers from
> > the master of the madduck.net zone, when querying
> > ns1.subdomain.madduck.net or ns2.subdomain.madduck.net, correct?
>
> sorry, i should have been more clear.
>
> by doesn't work, i mean that even though a dumpdb on the nameserver
> ns.madduck.net yields the following records:
>
> $ORIGIN madduck.net.
> subdomain 43200   IN      NS      ns1.subdomain.madduck.net.    ;Cl=3
>           43200   IN      NS      ns2.subdomain.madduck.net.    ;Cl=3
> $ORIGIN subdomain.madduck.net.
> ;mail   10743   IN      SOA     madduck.net. hostmaster.madduck.net. (
> ;               200107191 10800 3600 2592000 43200
> );madduck.net.;NXDOMAIN      ;-$     ;Cr=auth [194.25.0.125]
> ns1     43200   IN      A       192.168.14.13   ;NT=4 Cl=3
> ns2     43200   IN      A       192.168.14.14   ;NT=6 Cl=3
>
> and ns.subdomain.madduck.net, aside the cached data for madduck.net,
> it's dumpdb contains:
>
> $ORIGIN subdomain.madduck.net.
> mail    43200   IN      A       192.168.14.7    ;Cl=4
> ns1     43200   IN      A       192.168.14.13   ;Cl=4
> ns2     43200   IN      A       192.168.14.14   ;Cl=4
>
> > Have you verified that the madduck.net zone loads properly on the
> > master?
>
> yes.
>
> > You could try dumping the nameserver's database and verifying that the
> > glue records are in there.
>
> they are.
>
> now, i basically want to be able to resolve mail.subdomain.madduck.net
> through nameserver 192.168.14.1. recall that 192.168.14.1 is
> ns1.madduck.net and 192.168.14.13 is ns1.subdomain.madduck.net.
>
> thus, from a machine 192.168.14.2 (192.168.14.1 is the default
> nameserver):
>
>   fishbowl:~> host mail.subdomain.madduck.net 192.168.14.4
>   mail.subdomain.madduck.net   A       192.168.14.7
>
>   ===> on the subdomain NS, mail resolves!
>
>   fishbowl:~> host mail.subdomain.madduck.net
>   mail.subdomain.madduck.net does not exist (Authoritative answer)
>
>   ===> on the main NS, mail.subdomain is not found.
>
>   fishbowl:~> host -t ns subdomain.madduck.net
>   subdomain.madduck.net        NS      ns1.subdomain.madduck.net
>
>   ===> it looks as if the main domain correctly delegates to another
>        nameserver ...
>
>   fishbowl:~> host ns1.subdomain.madduck.net
>   ns1.subdomain.madduck.net     A       192.168.14.4
>
>   ===> ... which is also correctly glued in the main zone.
>
>   hbowl:~> host -t ns subdomain.madduck.net 192.168.14.13
>   subdomain.madduck.net        NS      ns1.subdomain.madduck.net
>
>   ===> the subdomain's NS also knows about it's NS delegation ...
>
>   fishbowl:~> host ns1.subdomain.madduck.net 192.168.14.13
>   ns1.subdomain.madduck.net     A       192.168.14.13
>
>   ===> ... and can obviously resolve it.
>
> so it looks as if everything was alright, and nevertheless, through
> the main NS, i can't resolve names in the subdomain. why? why? why?
>
> also, once mail.subdomain resolves, will i have problems with things
> like www.mail.subdomain? no, right?
>
> martin;              (greetings from the heart of the sun.)
>   \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net at madduck
> --
> de gustibus non est disputandum.