<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Jun 14, 2016, at 2:27 PM, David R Huberman <<a href="mailto:daveid@panix.com" class="">daveid@panix.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div class="">John,<br class="">
<br class="">
Thank you for the reply. You wrote:<br class="">
<br class="">
<blockquote type="cite" class="">Actually, this issue has originated not with staff, but from a significant<br class="">
number of folks who have found themselves no longer able to update<br class="">
the DNS servers (or origin AS) for a legacy network block, either though<br class="">
they were the original technical contact.<br class="">
</blockquote>
<br class="">
Wait. That's by design, isn't it?<br class="">
<br class="">
If Block X is registered to Company Y, then any authorized employee of Company Y can update the rDNS or origin_AS through normal channels. Anyone complaining they _can't_ update is *possibly* unauthorized (and therefore should go through ARIN's procedures).
Right?</div>
</div>
</blockquote>
<br class="">
</div>
<div>David - </div>
<div><br class="">
</div>
<div>Slightly more convoluted case (and obviously this is predominantly an </div>
<div>issue with legacy address blocks that have been long ignored…) </div>
<div><br class="">
</div>
<div>Jim Smith gets an /24 for his networking company “Sprockets” in 1994, </div>
<div>so that he can connect to the Internet. He gets /24) and connects to</div>
<div>the Internet via one the early commercial ISPs. </div>
<div><br class="">
</div>
<div>The netblock reads as follows:</div>
<div><br class="">
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>Sprockets</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>4131 El Camino Real, Palo Alta CA</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>X.Y.Z/24</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>Jim Smith</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span><a href="mailto:jim@well.com" class="">jim@well.com</a></div>
<div><br class="">
</div>
<div>Apparently, Jim left Sprockets sometime in the late 90’s… </div>
<div><br class="">
</div>
Twenty years later, Jim has called and is very upset with ARIN for having
<div class="">“munged it" all up - <br class="">
<div class=""><br class="">
</div>
<div class="">1) The organization field is set to “Sprockets”, not him.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">2) The Admin Contact for the organization says CKN-23</div>
</div>
<div class=""><br class="">
</div>
<div class="">3) While he would swear he was the tech contact on the Sprockets org</div>
<div class=""> (he still has his Well email and updated the DNS servers around 2005 </div>
<div class=""> to a friend’s DNS server), but for for some reason it now says CKN-23 </div>
<div class=""> for Tech Contact and he can’t regain control of the Sprockets org record.</div>
<div class=""><br class="">
</div>
<div class="">4) He is now listed only as the Abuse contact.</div>
<div class=""><br class="">
</div>
<div class="">Jim’s not a happy camper, and wants to know why ARIN disassociated him</div>
<div class="">with his address block randomly sometime after 2010. Jim says that he’s </div>
<div class="">been been using the address block for his house since leaving Sprockets </div>
<div class="">(no public IP, but he just uses NAT and connects via his public cable modem </div>
<div class="">IP address.) </div>
<div class=""><br class="">
</div>
<div class="">ARIN has very much has disassociated him from the address block, and </div>
<div class="">actually may not let him recover the IP address block until he’s recovered </div>
<div class="">Sprockets. Sprockets may have melted down, been sold, etc. and it is not</div>
<div class="">clear that Jim has any paperwork that covers his exit, use of the IP block,</div>
<div class="">or anything that happened to Sprockets. Because we no longer allow him</div>
<div class="">as a abuse contact to update the DNS servers, he can’t even use “his” IP</div>
<div class="">block now that he’s getting a nice new Internet connection.</div>
<div class=""><br class="">
</div>
<div class="">Does that help clarify the typical concern that we’re hearing from some legacy</div>
<div class="">address holders over our CKN23 database changes over the years?</div>
<div class=""><br class="">
</div>
<div class="">/John</div>
</div>
<div class=""><br class="">
</div>
</body>
</html>