Google weird routing?

Matt Harris matt at netfire.net
Thu May 23 20:59:53 UTC 2019


On Thu, May 23, 2019 at 3:44 PM Christopher Morrow <morrowc.lists at gmail.com>
wrote:

> On Thu, May 23, 2019 at 4:11 PM Matt Harris <matt at netfire.net> wrote:
> > On Thu, May 23, 2019 at 3:06 PM Christopher Morrow <
> morrowc.lists at gmail.com> wrote:
> >>
> >> 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       172.217.26.228
> >
>
> that's an ip in india alright :)
> I don't see why that's happening (in quick searching).
>
> >
> > Hoping someone over there can shed some light on why they are sending my
> packets on a world trip.  :)
>
> I'd be cuirous about:
>   dig www.google.com @8.8.8.8
>
> as well, please (jared's question as well)
>

Interestingly...


user at host # dig www.google.com @8.8.8.8

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> www.google.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2110
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.google.com.                        IN      A

;; ANSWER SECTION:
www.google.com.         299     IN      A       216.58.203.164

;; Query time: 16 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu May 23 16:55:04 EDT 2019
;; MSG SIZE  rcvd: 59

user at host   # host 216.58.203.164
164.203.58.216.in-addr.arpa domain name pointer bom07s11-in-f4.1e100.net.

Still comes back with a bom* host, so it looks like it's not based on the
DNS recursion server used.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190523/467aa9a4/attachment.html>


More information about the NANOG mailing list