nanog mailing list archives
Re: ARIN co-located nameserver problem
From: prue () ISI EDU
Date: Tue, 8 Dec 1998 14:11:52 -0800
...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
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)