Re: ARIN co-located nameserver problem
...Presumably in this case, you are responsible for that nameserver and therefore the /32 should be SWIP'd to you.
I do not see this as a valid assumption. It may well be that you don't want to be bothered with DNS maintenance or you don't trust your own network engineers to do DNS right and that you want to pay, say Paul Vixie, to do your DNS for you. His name and the quality of his DNS knowledge will add credulity to your network service. This works out so well, that Paul decides to sell this as a service to many small/medium size ISP's, running it on a single server. Now one /32 is the name server for multiple networks. So the registration system must be able to deal with that. This is not an unreasonable scenario. Walt Prue
On Tue, 8 Dec 1998 prue@ISI.EDU wrote:
...Presumably in this case, you are responsible for that nameserver and therefore the /32 should be SWIP'd to you.
so well, that Paul decides to sell this as a service to many small/medium size ISP's, running it on a single server. Now one /32 is the name server for multiple networks. So the registration system must be able to deal with that. This is not an unreasonable scenario.
In this case Paul would not SWIP the /32 at all since he maintains the responsibility for the server. Presumably then he would handle the registration of the nameserver address with ARIN and the original problem would not occur since the registration application is coming from the entity with administrative control over the IP address in question. -- Michael Dillon - E-mail: michael@memra.com Check the website for my Internet World articles - http://www.memra.com
participants (2)
-
Michael Dillon -
prue＠ISI.EDU