Re: [Starlink] Starlink Digest, Vol 25, Issue 28

[Michael Richardson <mcr@sandelman.ca>]

David Fernández via Starlink wrote:
    > As we were discussing recently, maybe starting with anycast DNS
    > servers on satellites is a first step to consider, before embarking
    > any other type of cloud servers.

For Starlink customers, having a DNS recursive cache on the satellite you are
talking to certainly saves half a hop, if the cache is big enough.
If the gateway part of the bent pipe suffers from bufferbloat,
then having DNS queries from the client avoid that part seems like a win.
Also, the recursive queries from the DNS recursive cache can be switched on a
different circuit to the gateway, or marked better to avoid the bufferbloat.

{or, you know, you could fix the bloat. In the satellite to satellite laser
circuits, I suspect that the bandwidth available will fluctuate wildly.
Engineers will be reluctant to throw away delay tolerant packets in that case}

(I'm not sure we should call it an anycast DNS service, because even though
it looks similiar to the clients to the things we do with BGP, its not really
the same.  Also, squatting on/intersepting 8.8.8.8, etc. would be a very bad
thing to do.  It would have to be a new address. But, because we wouldn't be
using BGP, it does not need to occupy an entire /24. )

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [