From: J Pan <Pan@uvic.ca>
To: David Lang <david@lang.hm>, Nathan Owens <Nathan@nathan.io>
Cc: Spencer Sevilla <spencer.builds.networks@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
"Livingood, Jason" <Jason_Livingood@comcast.com>,
Frantisek Borsik <frantisek.borsik@gmail.com>
Subject: [Starlink] Re: Lost in Space: The Limits of Geolocation in a Satellite-Connected World (new article from Geoff Huston)
Date: Wed, 1 Oct 2025 21:34:51 -0700 [thread overview]
Message-ID: <CAHn=e4gzctbT3mtOfrBdQWF4ViYJ7oP0dbcBOWrmmXBQj0X69w@mail.gmail.com> (raw)
In-Reply-To: <2518qp9p-1qrp-p185-1os8-qpo57s3s2n0q@ynat.uz>
the fault of the default
https://web.archive.org/web/20160410172437/http://fusion.net/story/287592/internet-mapping-glitch-kansas-farm/
a sad story all cs people shall read before code
similarly at starlink, who is moving their error-prone dns domain
pop.starlinkisp.net
origin = dns31.cloudns.net
mail addr = isp\.abuse.spacex.com
serial = 2025061904
refresh = 7200
retry = 1800
expire = 1209600
minimum = 3600
to
isp.starlink.com
origin = ns1-35.azuregov-dns.us
mail addr = azuredns-hostmaster.microsoft.com
serial = 1
refresh = 3600
retry = 300
expire = 2419200
minimum = 300
but the serial (number) is obviously default. @Nathan Owens alerted
already. hope it fixed
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Wed, Oct 1, 2025 at 4:05 PM David Lang via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> Spencer Sevilla wrote:
>
> > I could certainly see some use for IP-based geolocation going forward, less as
> > a concrete primary source and more as a cross-check on other location-based
> > tools for e.g. security purposes.
>
> between VPNs and just incomplete data in the geoip databases, it's questionable
> how useful this is as a security source (it's not worthless, but it's not worth
> a lot) see the poor farm in Kansas that gets all the attention from geoip based
> responses where only the country is known.
>
> David Lang
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
next prev parent reply other threads:[~2025-10-02 4:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 5:34 [Starlink] " Frantisek Borsik
2025-10-01 5:56 ` [Starlink] " J Pan
2025-10-01 16:46 ` Michael Richardson
2025-10-01 17:40 ` J Pan
2025-10-01 21:08 ` Michael Richardson
2025-10-01 22:50 ` J Pan
2025-10-01 13:18 ` Livingood, Jason
2025-10-01 21:22 ` David Lang
2025-10-01 21:51 ` Spencer Sevilla
2025-10-01 22:48 ` J Pan
2025-10-01 23:05 ` David Lang
2025-10-02 4:34 ` J Pan [this message]
[not found] ` <22339.1759337017@obiwan.sandelman.ca>
2025-10-01 16:47 ` Michael Richardson
2025-10-01 21:13 ` David Lang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHn=e4gzctbT3mtOfrBdQWF4ViYJ7oP0dbcBOWrmmXBQj0X69w@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=Jason_Livingood@comcast.com \
--cc=Nathan@nathan.io \
--cc=david@lang.hm \
--cc=frantisek.borsik@gmail.com \
--cc=spencer.builds.networks@gmail.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox