Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: ARIN co-located nameserver problem

  • From: Wayne
  • Date: Wed Dec 09 03:39:54 1998

At 12:23 PM -0800 12/8/98, Michael Dillon wrote:
On Tue, 8 Dec 1998, Dean Anderson wrote:

What about this policy of ARIN's--Do people think ARIN should be
registering nameservers by name or by IP address?  To make this work in
general, one would need to SWIP single IP addresses.
There was a discussion about what should be SWIP'd in Seattle and it
seemed that the conclusion was that SWIP policy should not be based on
block size. Instead it should be based upon whether or not network
operators need to know who is responsible for the network using that
block. Presumably in this case, you are responsible for that nameserver
and therefore the /32 should be SWIP'd to you. This does not mean that all
/32 assignments should be SWIP'd, just the occasional special ones like a
nameserver located on someone else's network.
That makes no sense.

It's really not ARIN's business what address space a nameserver lives on.

ARIN should be attaching IN-ADDR records to a NIC handle, and the owner of that NIC handle should be able to change the host's name and IP address inside that NIC whatever they want.




Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.