[governance] Small Sample of the IN-ADDR.ARPA and /8 Allocation Information

Mon Dec 26 19:34:38 EST 2005

For those people without tools to look in the DNS, here is a very small
sample of
what one finds in the IANA flatfile and the DNS for IN-ADDR.ARPA domain
names.
In this small sample, the U.S. Government's Postal Service appears to match
up.
In some cases there is no DNS entry (i.e. NXDOMAIN). In other cases, a
different
company or network appears. This is in an era when the U.S. Government is
passing
laws requiring that whois and other DNS information be accurate and
up-to-date.

http://www.iana.org/assignments/ipv4-address-space
038/8   Sep 94   Performance Systems International (COGENTCO.COM)
046/8   Dec 92   Bolt Beranek and Newman Inc. (NXDOMAIN)
047/8   Jan 91   Bell-Northern Research (NORTELNETWORKS.COM)
054/8   Mar 92   Merck and Co., Inc. (NXDOMAIN)
055/8   Apr 95   Boeing Computer Servicesn (ARMY.MIL)
056/8   Jun 94   U.S. Postal Service
057/8   May 95   SITA (EQUANT.NET)

46.in-addr.arpa NXDOMAIN

;; AUTHORITY SECTION:
38.in-addr.arpa.        10800   IN      NS      auth4.dns.cogentco.com.
38.in-addr.arpa.        10800   IN      NS      auth5.dns.cogentco.com.
38.in-addr.arpa.        10800   IN      NS      auth1.dns.cogentco.com.
38.in-addr.arpa.        10800   IN      NS      auth2.dns.cogentco.com.

;; AUTHORITY SECTION:
47.in-addr.arpa.        42452   IN      NS      ns-rch47.nortelnetworks.com.
47.in-addr.arpa.        42452   IN      NS      ns-ott47.nortelnetworks.com.

;; AUTHORITY SECTION:
55.in-addr.arpa.        3600    IN      NS      ns02.army.mil.
55.in-addr.arpa.        3600    IN      NS      ns03.army.mil.
55.in-addr.arpa.        3600    IN      NS      ns01.army.mil.

;; AUTHORITY SECTION:
56.in-addr.arpa.        3600    IN      NS      dns082.usps.com.
56.in-addr.arpa.        3600    IN      NS      dns100.usps.com.
56.in-addr.arpa.        3600    IN      NS      dns141.usps.com.

;; AUTHORITY SECTION:
57.in-addr.arpa.        86400   IN      NS      ns2.equant.net.
57.in-addr.arpa.        86400   IN      NS      ns3.equant.net.
57.in-addr.arpa.        86400   IN      NS      ns1.equant.net.
======

The above is a very small sample. Another interesting section is the address
space
labeled "Various Registries". In most of those sections the DNS shows ONE
Registry.
It is ironic that in the sections where ONE IANA Registry is shown,
*Various* Registries show
up in the DNS query. In some cases, experimental information appears to be
placed in
the DNS. In general, the entire mess appears to be some research project
which is no
longer maintained. In various UN and ITU and WSIS forums, there has been
wide-spread
agreement that the Internet is no longer a research project for the
priviledged few, mostly
in private universities.

128/8   May 93   Various Registries
;; AUTHORITY SECTION:
128.in-addr.arpa.       86400   IN      NS      indigo.arin.net.
128.in-addr.arpa.       86400   IN      NS      epazote.arin.net.
128.in-addr.arpa.       86400   IN      NS      figwort.arin.net.
128.in-addr.arpa.       86400   IN      NS      chia.arin.net.
128.in-addr.arpa.       86400   IN      NS      dill.arin.net.
128.in-addr.arpa.       86400   IN      NS      basil.arin.net.
128.in-addr.arpa.       86400   IN      NS      henna.arin.net.

041/8   Apr 05   AfriNIC
;; AUTHORITY SECTION:
41.in-addr.arpa.        172800  IN      NS      ns1.afrinic.net.
41.in-addr.arpa.        172800  IN      NS      sec1.apnic.net.
41.in-addr.arpa.        172800  IN      NS      sec3.apnic.net.
41.in-addr.arpa.        172800  IN      NS      ns-sec.ripe.net.
41.in-addr.arpa.        172800  IN      NS      tinnie.arin.net.
41.in-addr.arpa.        172800  IN      NS      ns.lacnic.net.

;; ANSWER SECTION:
62.in-addr.arpa.        3600    IN      TYPE48  \# 262
010103050103F349374086042
566F7928F017BED0DF7DBE615A081B1
FD0D23615A81DC42F63A5C745693CB5D2AC9CE0197014850
F1B95524 F47B8B47208096CB3DB9480BB207D1C2BDF73B6AF290813E4189A52A
5BADDDD6D02B5C
39C0118B68906390E6711E7D522987D9846D3AFD4B
99C1EAA4BC0E2ED9EE9FC6743D4C3E5CD2976
A3FEA0508428BA786E5 46055EDBF7DBC97D41E4298D345212AA312DB9B27D5430D6EA90615E
671
B9A8D1E8A428372013641707C84E002E48B41DFBCCF47E2F43115
78800EBDAFE7287EAA19CDE717
62005ABE367C86FC5377EE8E2891D5
D226580A8967F3F52A0D53327CCF82E15C1E8B8D82B3545F8
895017C CFBEA2CCE612AE0964D1
62.in-addr.arpa.        3600    IN      TYPE48  \# 156
010003050103B17B59DDF5582
EE41E3B8C79EFF0B910F36522D6BCDA
6B9FD1B637814D349806CB5C974889B1D49D42B8A747285A
B05F14BB CEB28253C0CFF7E238F7B3C48FD4FE26F458DFAC6D458D1C1AFF98D1
D4C0432DF30320
A6CA3255B13E78EAD36EC96894023AA84FAD933DDF
2F11F63E1EAB1A495CE9C9A9A7C2CF4490BEF
6FD3651F38C4F0C34A3 DD6178A4EFA06019FB1FD1CDB2F39E2D

====

Looking ahead to the future, one area that appears to still be stuck in the
past is the
use of address space to trigger protocols such as MultiCast. That is an
architectural wart
because it uses valuable address space, for protocols which are not widely
used. Also
MultiCast can be done in a variety of ways with any addresses and may rely
on DHT.
Again, this appears to be something left over from an academic research
project.
The MultCast code has been removed from high-performance routers and even
consumer
devices. Looking at the DNS it now appears that "Various" companies are
starting to use
the /8s now re-purposed from the legacy DARPA network days, where R was for
Research.

224/8   Sep 81   IANA - Multicast
225/8   Sep 81   IANA - Multicast
226/8   Sep 81   IANA - Multicast
...
237/8   Sep 81   IANA - Multicast
238/8   Sep 81   IANA - Multicast
239/8   Sep 81   IANA - Multicast

;; AUTHORITY SECTION:
224.in-addr.arpa.       42561   IN      NS      flag.ep.NET.
224.in-addr.arpa.       42561   IN      NS      strul.stupi.se.
224.in-addr.arpa.       42561   IN      NS      nic.near.NET.

_______________________________________________
governance mailing list
governance at lists.cpsr.org
https://ssl.cpsr.org/mailman/listinfo/governance