From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 256F43B29E for ; Fri, 14 Apr 2023 10:47:47 -0400 (EDT) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 33EElgA3043556; Fri, 14 Apr 2023 07:47:42 -0700 (PDT) (envelope-from starlink@gndrsh.dnsmgr.net) Received: (from starlink@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 33EElgvA043555; Fri, 14 Apr 2023 07:47:42 -0700 (PDT) (envelope-from starlink) From: "Rodney W. Grimes" Message-Id: <202304141447.33EElgvA043555@gndrsh.dnsmgr.net> In-Reply-To: To: Dave Taht Date: Fri, 14 Apr 2023 07:47:42 -0700 (PDT) CC: Dave Taht via Starlink X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 14:47:48 -0000 > "The Kepler Network will streamline on-orbit communications with a > network infrastructure designed to act as Internet exchange points > (IXP) for space-to-space data relay. The Internet-ready constellation > will deliver data to and from spacecraft in real time, enabling > high-speed data relay through SDA-standard optical terminals." > > https://kepler.space/2023/04/13/kepler-raises-92-million-usd-series-c-to-complete-internet-ready-optical-constellation/ > > 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. -- Rod Grimes rgrimes@freebsd.org