[194494] in North American Network Operators' Group
Re: GEO LOCATION
daemon@ATHENA.MIT.EDU (Jared Mauch)
Wed May 3 08:35:05 2017
X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAAtHPf8zC-rCPz5Mh-RL0Eigu-r7TKj96AsYUtGqb+LGVPJgyw@mail.gmail.com>
Date: Wed, 3 May 2017 08:32:48 -0400
To: Chris Lane <clane1875@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
> On May 3, 2017, at 8:27 AM, Chris Lane <clane1875@gmail.com> wrote:
>=20
> All
>=20
> We have several direct allocations from ARIN which we then provide =
smaller
> prefixes to our customers across the country. Our HQ is on the East =
coast,
> but many of our customers are on the West Coast. Trying to understand =
and
> fix some of my west coast customers GEO LOCATION issues as they are
> reporting for instance when running "speed tests" to Internet sites =
the
> location pops up as an East Coast server instead of West and more =
local.
A number of CDNs use tools like the DNS server/query source to identify =
where
the clients are. If they are all using a centralized DNS server, some =
providers
will classify you as in one area vs another.
Consider using a different DNS query-source for east coast vs west coast
users. Consider using tools like ECS (EDNS0-Client-Subnet) if possible =
to
provide hints to the various CDNs/Geolocation folks.
If you=E2=80=99re aware of a specific mis-charachtherisation, consider =
posting the
relevant DNS server information or IP ranges involved.
If you don=E2=80=99t know how to find your DNS server query-source, a =
tool like this:
https://cmdns.dev.dns-oarc.net/
Will help you find the information easily.
- Jared=
