From owner-freebsd-chat Fri Oct 18 1:47:52 2002 Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFCAE37B401 for ; Fri, 18 Oct 2002 01:47:50 -0700 (PDT) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7624F43E9E for ; Fri, 18 Oct 2002 01:47:50 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0032.cvx21-bradley.dialup.earthlink.net ([209.179.192.32] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 182SnG-0007EH-00; Fri, 18 Oct 2002 01:47:42 -0700 Message-ID: <3DAFCA67.BD903D01@mindspring.com> Date: Fri, 18 Oct 2002 01:46:31 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Darren Pilgrim Cc: Doug White , "Kevin D. Kinsey, DaleCo, S.P." , Dave Rossow , freebsd-chat@FreeBSD.ORG Subject: Re: Verisign dns trick References: <20021017150438.I88254-100000@carver.gumbysoft.com> <3DAFAFE5.6B558470@pantherdragon.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Darren Pilgrim wrote: > Doug White wrote: > > Of course, if you use a non-verisign aligned registrar, host adds and > > domain updates usually happen instantaneously so the registration burden > > is much less :) > > Can you name a few? Looking for a registrar that allows one to have > multiple domains with differing registrant information in the same > account, has a reasonable update time, and isn't a Verisign puppet has > proven difficult. Whoever controls the top level DNS controls all the DNS; that's just the way it is. Currently, that's ICANN. It doesn't matter who you go with, ICANN gets their pound of flesh. That's why there is no real protocol defined to register domain names, and why a domain registration can't be completed within a browser timeout: if you have a monopoly, there's no incentive to improve service. The way the registrars that update more quickly operate is to set up their own servers to update from, and forward to the real ones, until the real ones are up: basically, name servers have to be registered within an ASN before they are really there, as far as the root is concerned. As to who does it correctly: no one: it's not permitted that it be run correctly. As to who comes close: it really depends: as soon as any registrar hits a critical mass, the overhead will exceed their ability to process, and it will go to hell, just like the one you leave behind, because it went to hell. Yeah, I'm a little cynical: I tried to get an RFC in for an update and registration protocol that would work in under 1/2 a browser timeout, for registration of new domains, all the way back in 1996, when I saw this was going to be a problem. I guess at least I get the "I told you so", which is poor consolation, indeed. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message