nanog mailing list archives
Re: ARIN co-located nameserver problem
From: Michael Dillon <michael () memra com>
Date: Tue, 8 Dec 1998 12:23:05 -0800 (PST)
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. -- Michael Dillon - E-mail: michael () memra com Check the website for my Internet World articles - http://www.memra.com
Current thread:
- ARIN co-located nameserver problem Dean Anderson (Dec 08)
- Re: ARIN co-located nameserver problem Michael Dillon (Dec 08)
- Re: ARIN co-located nameserver problem Wayne (Dec 09)
- Re: ARIN co-located nameserver problem Randy Bush (Dec 09)
- Re: ARIN co-located nameserver problem Karl Denninger (Dec 09)
- Re: ARIN co-located nameserver problem Wayne (Dec 09)
- Re: ARIN co-located nameserver problem Michael Dillon (Dec 08)
- <Possible follow-ups>
- Re: ARIN co-located nameserver problem prue (Dec 08)
- Re: ARIN co-located nameserver problem Michael Dillon (Dec 08)
- Re: ARIN co-located nameserver problem Dean Anderson (Dec 08)
- Re: ARIN co-located nameserver problem Kim Hubbard (Dec 09)
- Re: ARIN co-located nameserver problem Dean Anderson (Dec 09)