[ppml] Comments on ARIN's reverse DNS mapping policy

[Jon Lewis]

On Tue, 11 Sep 2007, John Von Essen wrote:

> Now consider this...
>
> # nslookup 76.161.191.192
> ;; connection timed out; no servers could be reached
>
> And the above took about 20 seconds to return. The AS who advertises 
> 76.161.192.0/24 (and many other /24's) does not have the 
> 192.161.76.in-addr.arpa zone configured at all on their DNS server. This is a 
> problem for the user of that IP, and any person on the internet that has to 
> talk to that IP since it will create a burdensome dns timeouts.
>
> I'm sorry, but that second example is simply unacceptable. This may sound 
> rude, but the amount of money ARIN brings in for ASN registrations, 
> membership, and IP range allocations - the buck has to stop with ARIN when it 
> comes to AS's who completely misconfigure massive in-addr.arpa zones and 
> potentially create the environment to slow down dns traffic throughout the 
> internet.

ARIN hands out IP space and ASNs.  Other than some general rules as to 
what ARIN members can do with their IP space, ARIN doesn't tell them how 
to run their networks.

Annoying as it may be, if you don't like the way your ISP runs _their_ 
network, you have two choices.

1) Leave.
2) Buy them and run the network your way.

If you want ARIN to start imposing rules on how members do things, make it 
something useful and have ARIN forbid BGP deaggregation of allocated / 
assigned CIDRs into subnets having the same as-path.

----------------------------------------------------------------------
  Jon Lewis                   |  I route
  Senior Network Engineer     |  therefore you are
  Atlantic Net                |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________