[25596] in North American Network Operators' Group
Re: DNS for 16.172.in-addr.arpa
daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Thu Oct 21 18:36:50 1999
From: bmanning@vacation.karoshi.com
Message-Id: <199910212301.QAA05326@vacation.karoshi.com>
To: atatat@atatdot.net
Date: Thu, 21 Oct 1999 16:01:05 -0700 (PDT)
Cc: grisha@verio.net, nanog@merit.edu
In-Reply-To: <19991021175921.A21710@noc.untraceable.net> from "Andrew Brown" at Oct 21, 1999 05:59:21 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
>
> well...imho, they should be delegated to localhost. and everyone
> should have a localhost zone with the proper address in it, to go with
> their 127.in-addr.arpa zone file.
>
> but then again, some people think i'm weird.
>
> --
Well, in that context all of RFC 1918 space should never have
been delegated and private networks built out of 127.0.0.0/8.
In the mists of time, I actually built a network that way.
Seems that the prevaling wisdom was to delegate whole other
blocks for tom-foolery. Given the lax registration checking,
it was considered prudent to actually have real servers host
these zones so the possiblity of "hijacking" would be reduced.
There was a recent attempt to actually have the servers provide
an authoritative response when a query was received. This engendered
a significant raft of unexpected responses. Apparently several
fortune 1000 companies have used this space for network mgmt.
and propogate the prefixes in the Internet. This will be much
to their dismay when authoritative replies are once more available.
YMMV.
