> Hi and Thanks a lot to all of you who helped out.
>
>
> After following the steps explained by you (like changing the MNAME
> record for my delegated zone) and Adding an A record for
> ns.dgtlplayground.vodha. (the delegated zone) which before has been a
> CNAME RR:
>
> Before:
> dgtlplayground.vodha. IN A 192.168.100.201
> ns.dgtlplayground.vodha. IN CNAME dgtlplayground.vodha.
>
> After:
> ns.dgtlplayground.vodha. IN A 192.168.100.201
>
> Delegation works fine, both for reverse zones (in-addr.arpa) and
> "normal" zones (dgtlplayground.vodha.).
>
>
> Now there's still a question about delegation that I find unanswered
> (and still not asked).
>
> The O'Reilly DNS and BIND book, which I find informative, says about
> delegating reverse zones:
>
> (a not-really-a-quotation-quotation) "We almost forgot to delegate the
> 254.253.192.in-addr.arpa zone! This is little trickier than delegating
> fx.movie.edu (the example zone from the book) because we don't manage
> the parent zone. [...] As it turns out the in-addr.arpa zone is the
> parent. [...] So all that is left is to contact ARIN and tell them to
> delegate different." (or something like that.)
>
> This is only correct for internet addresses? I.e. not for 192.168.x.x
> (and friends), so when delegating local addresses, it will do with a
> stub zone, like:
>
>
> zone "100.168.192.in-addr.arpa" {
> type stub;
> notify no;
>
> masters { 192.168.100.201; };
>
> forwarders { };
>
> file "192.168.100.stub";
> };
>
>
> when I was to make this by hand, how would the delegation entries look
> like (glue record 'n stuff) for 192.168.100.x? Would I have to add a
> zone like 192.168.in-addr.arpa, to be a parent zone of
> 192.168.100.in-addr.arpa? But 192.168.in-addr.arpa, isn't the parent of
> 192.168.100.in-addr.arpa, right? (see quotation above) And how would the
> zone statement in named.conf look like for manual delegation of
> 192.168.100.x?
>
>
>
> Mikael Olenfalk
> mikael@xxxxxxxxxxxxx (www.netgineers.se)
Generally I would just have all the internal servers serve
168.192.in-addr.arpa delegate 100.168.192.in-addr.arpa
from that. As 168.192.in-addr.arpa is the top of this
block of private address space it doesn't get delegated to.
If you have a server that is not going to be a slave / master
for 168.192.in-addr.arpa then you would make it a stub. However
I strongly recommend just using slave and master zones for
168.192.in-addr.arpa and the other top level RFC 1918 reverse
zones 10.in-addr.arpa, 16.172.in-addr.arpa - 31.172.in-addr.arpa.
Note you need to reverse the order of the octets in the IP
address when creating the name of the reverse zone.
Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@xxxxxxx
|
