[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: ietf-provreg@cafax.se
From: Kent Crispin <kent@songbird.com>
Date: Fri, 6 Apr 2001 09:59:30 -0700
In-Reply-To: <a05100905b6f399398742@[10.10.20.173]>; from Jordyn A. Buchanan on Fri, Apr 06, 2001 at 12:06:19PM -0400
Mail-Followup-To: ietf-provreg@cafax.se
Sender: owner-ietf-provreg@cafax.se
Subject: Re: Nameserver MUST HAVE IP

On Fri, Apr 06, 2001 at 12:06:19PM -0400, Jordyn A. Buchanan wrote:
> If you are the authoritative registry for a TLD and you don't have 
> the IP address of a name server within your TLD, how can the NS's IP 
> address possibly be found through a "normal lookup"?

I think that the examples cited by Elmar and others have explained this
pretty well -- the NS's are in different SLD's, but within the same TLD. 

This situation is extremely common -- in fact, it may be the usual case:
a web hosting company may provide name service for hundreds of SLDs with
nameservers within its own domain, and no glue is needed for any of
those SLDs.  Or consider all those parked domains...

> The IP address is only a required element for name servers within the 
> registry's authoritative TLDs.  For nameservers within other TLDs, 
> they are not required (indeed, I think they're prohibited).

The reasoning is recursive?

Kent

-- 
Kent Crispin                               "Be good, and you will be
kent@songbird.com                           lonesome." -- Mark Twain

Home | Date list | Subject list