From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (unknown [66.167.227.145]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C47003B29E for ; Fri, 14 Apr 2023 15:36:47 -0400 (EDT) Received: from dlang-mobile (unknown [10.2.2.69]) by mail.lang.hm (Postfix) with ESMTP id 63333185D27; Fri, 14 Apr 2023 12:36:46 -0700 (PDT) Date: Fri, 14 Apr 2023 12:36:46 -0700 (PDT) From: David Lang To: "Rodney W. Grimes" cc: Dave Taht , Dave Taht via Starlink In-Reply-To: <202304141447.33EElgvA043555@gndrsh.dnsmgr.net> Message-ID: References: <202304141447.33EElgvA043555@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Re: [Starlink] fiber IXPs in space X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Apr 2023 19:36:47 -0000 On Fri, 14 Apr 2023, Rodney W. Grimes via Starlink wrote: >> I keep wondering when or if Nasa will find a way to move their DNS >> root server "up there" . DNS data is not all that much... it is the >> original distributed database... > > As others have pointed out a "root server" may not be very advantages, > but what I think would be far better is to put up a couple of anycast > recursive caching resolvers, aka 8.8.8.8/8.8.4.4 and almost anyone > can do that, including starlink itself. I believe that the root servers are all (or almost all) anycast nowdays. David Lang