Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!rutgers!sunybcs!boulder!huntting
From: huntting@sel.bldrdoc.gov (Brad Huntting)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re:  in-addr.arpa domains outside the USA.
Summary: Perhaps some distribution of in-adder.arpa is needed...
Message-ID: <21626@boulder.Colorado.EDU>
Date: 29 May 90 01:59:03 GMT
References: <9005281622.AA00948@Gipsi.Gipsi.Fr>
Sender: news@boulder.Colorado.EDU
Distribution: inet
Organization: NOAA / Space Environment Lab
Lines: 28


If the NIC would franchise authority for network numbers, It could
allow them to be distributed on a *local* connectivity basis instead
of global.

Thus (for example) an Albanian network authority would be given
the 234.in-addr.arpa domain (and maybe some others), keep the
SOA for it (on a well connected node), and give out IP numbers
234.xxx.yyy.0 to local interests.

Delegating other nameservers for the in-addr domain based on region
could improve BIND performance, and reduce network traffic in general.

For example, all (new) class C nets in Lebanon Kansas will start with
128, and the nameservers for 128.in-addr.arpa are also in Lebanon.
This assumes most of the hosts in Lebanon are near each other (in the
network sense).

This would distribute some of the load of the in-addr.arpa domain
away from the root, and cut down on unnecessary long haul queries.

Root nameservers would be queried less often for near by reverse
mapping.


brad
      huntting@boulder.colorado.edu
      huntting@sel.bldrdoc.gov