Google weird routing?
fhr at fhrnet.eu
Thu May 23 20:24:30 UTC 2019
Google maintains their own GeoIP database. If you peer with them and have access to the peering portal, you can correct the location yourself.
Otherwise they have a public form somewhere.
On 23 May 2019 10:11:30 pm GMT+02:00, Matt Harris <matt at netfire.net> wrote:
>On Thu, May 23, 2019 at 2:55 PM Jared Mauch <jared at puck.nether.net>
>> I would say that it says BOM at the start of the name, perhaps they
>> sending you to India?
>> Are you using a DNS service that uses ECS facing the various
>> providers or a different one?
>This is my thinking, too, however my recursive DNS servers are all on
>same network as the systems trying to reach google, all of which are on
>space that I own and announced exclusively by AS 394102 here in the US.
>I've also taken care to maintain as many geoip service entries as could
>found/maintained, including maxmind's. Where they would get the idea
>my packets should go to India is beyond me.
>On Thu, May 23, 2019 at 3:06 PM Christopher Morrow
><morrowc.lists at gmail.com>
>> not sure where you are starting from (really) .. can you provide a:
>> dig www.google.com
>> for me? My guess is that as Jared noted you got somehow looking like
>> you are in india to whatever does that magic :)
>Google's coming back with bom* addresses; no idea why though.
>;; ANSWER SECTION:
>www.google.com. 300 IN A 184.108.40.206
>Hoping someone over there can shed some light on why they are sending
>packets on a world trip. :)
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG