[35311] in North American Network Operators' Group
Re: new.net: yet another dns namespace overlay play
daemon@ATHENA.MIT.EDU (Joe Provo)
Tue Mar 6 18:24:24 2001
Date: Tue, 6 Mar 2001 15:39:39 -0500
From: Joe Provo <joe.provo@rcn.com>
To: nanog@merit.edu
Message-ID: <20010306153939.B24268@ultra.net>
Reply-To: joe.provo@rcn.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.BSF.4.21.0103061131580.56422-100000@localhost>; from patrick@cybernothing.org on Tue, Mar 06, 2001 at 11:36:42AM -0800
Errors-To: owner-nanog-outgoing@merit.edu
On Tue, Mar 06, 2001 at 11:36:42AM -0800, Patrick Greenwell wrote:
> On Tue, 6 Mar 2001, Joe Provo wrote:
> > Too bad people can believe what they read in press releases rather than
> > reality.
> >
> > I wonder if anyone can register a name with them, and then sue them for
> > not actually adding any new TLDs?
>
> They are adding new TLDs via their own root servers.
>
> http://www.new.net/help_isp_info.tp
>
> Everyone that has a computer has a choice where to point resolution to.
Yup, and that page is the tweak-your-nameserver for those who want to
dictate that clients see an inconsistant view of the net. Note the
end-user instructions (http://www.new.net/download/instructions_unknown.tp)
clearly indicate to just add extend the search zone, or subvert your
resolver on windoze from a browser widget.
Interesting how this will play into Earthlink's "provider of the real
internet" advertizing... is providing an inclusively inconsistant view
of the namespace more real than doing so by exclusion? :-) Is an
inconsistant namespace "worse" than transparent caching, or other "not
real Internet" practices? Either way, it becomes a matter of end-user
confusion. Personally, I think this will be the significant 'secession'
from the current collective DNS tree that other attempts have not been.
Joe,
just throwing out thoughts, not judging either...
--
Joe Provo Voice 508.486.7471
Director, Internet Planning & Design Fax 508.229.2375
Network Deployment & Management, RCN <joe.provo@rcn.com>
