Best Reverse lookup config, APNIC vs RIPE.

[Barry Margolin]

In article <Pine.WNT.4.21.0004272317560.-4055753-100000 at hades.sarnic.hk.com>,
Maren S. Leizaola <leizaola at sarnic.hk.com> wrote:
>
>Hi,
>	I've just examined the two configurations of networks
>213.in-addr.arpa (RIPE) and 203.in-addr.arpa.
>
>RIPE for this network have configured all the delegations in a single zone
>file and specify two octets in the zone file to delegate a single class
>'C' Eg. :
>
>130.158                 5D IN NS        ns.arpanet.ch.
>                        5D IN NS        ns2.arpanet.ch.
>                        5D IN NS        domc1.arpanet.ch.
>129.158                 5D IN NS        ns.arpanet.ch.
>                        5D IN NS        ns2.arpanet.ch.
>                        5D IN NS        domc1.arpanet.ch.
>
>which are equal to networks 213.158.130 and 213.158.129
>
>
>APNIC at the top level only list the octet and delegate each network back
>to themselves.
>
>185.203.IN-ADDR.ARPA.   4D IN NS        svc00.apnic.net.
>                        4D IN NS        ns.apnic.net.
>
>
>
>Which one of the two is better?

The main benefit of the second approach is that modifications are a little
more efficient.  When making a change to a 203.185.x reverse delegation,
the primary server only needs to reload a small 185.203.in-addr.arpa zone
file, and the secondary server only has to transfer that small zone, rather
than reloading and transfering an enormous 203.in-addr.arpa zone file.

An even more exteme case is ARIN.  They put all their delegations directly
in the IN-ADDR.ARPA zone!

-- 
Barry Margolin, barmar at genuity.net
Genuity, 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 group.