Reverse zone delegation for 172.16.16.0/20 - HOW TO?
Ellad G. Yatsko
eyatsko at ngs.ru
Mon May 21 06:36:38 UTC 2012
Sorry, it is my mistake. What is about the simpliest diagram? :-)
(Regional Site) 172.16.0.0/16 . . . . . . . .
(Regional Site) 172.30.0.0/16
. . . . . . . . (Local Site) 172.16.16.0/20 . . . . . . .
. . . . . . . . . (Local Site) 172.30.32.0/20 . . . . .
. . .
Central delegates to Regional /16 block, Reginal to Local /20.
In terms of forward zone delegation it would be:
united-networks.ru (Central) -> msk.united-networks.ru (Regional,
Moscow) -> sokol.msk.united-networks.ru (district in Moscow City).
united-networks.ru (Central) -> abakan.united-networks.ru (Regional,
Khakasia republic with Abakan as capital, Russia)->
kurochkina.abakan.united-networks.ru (district in Abakan).
So I thought to set up reverse delegation by analogy with this.
The below article doesn't answer on question how to formalize /20
delegation. Instead it shows how to make < /24 delegation.
> You don't set up the /12 zone at all.
> You haven't made it clear what the relationships are between the sites,
> and who needs to resolve what. You also haven't made clear where the
> resolving name servers are for these sites. In order to help we really
> need more information about what you're trying to accomplish.
>> I used a trick and made zone 172.in-addr.arpa. It is not exact but it
> You really don't want to do that.
>> But I can't at all to delegate block 172.16.0.0/16 to second level
>> server to say nothing about delegation 172.16.16.0/20 from second level
>> to ending DNS!
> You probably don't want to delegate them at all, you probably want to
> just set up the /16 zones on the appropriate local server. If other
> sites need to resolve the addresses for a /16 assigned to one city,
> there are various ways that this can be accomplished, but as I said
> above we need to know more about what you're trying to do.
> For delegation of the /20 zones, see:
More information about the bind-users