[178933] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Google served from non-google IPs?

daemon@ATHENA.MIT.EDU (manning)
Sat Mar 14 16:22:01 2015

X-Original-To: nanog@nanog.org
From: manning <bmanning@karoshi.com>
In-Reply-To: <CAFJiuFqZZxnxJxGy4yreMa0n0z=_WWP337qvqj4BNcQQ3S1vNg@mail.gmail.com>
Date: Sat, 14 Mar 2015 13:16:37 -0700
To: Dave Temkin <dave@temk.in>
X-MailScanner-From: bmanning@karoshi.com
Cc: Jason Lixfeld <jason@lixfeld.ca>, NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

one of the legacy uses of an IX was to place =93content=94 near the =
eyeballs.   For the adventurous, this meant placing NTP chimers, DNS & =
route servers,
and even content directly on the switch mesh.  Akamai might have been =
the first to pull back from that and move its services behind an Akamai =
router
that was on the switch mesh.

These days, most folks use BGP =93condoms=94 to protect themselves.

manning
bmanning@karoshi.com
PO Box 12317
Marina del Rey, CA 90295
310.322.8102



On 14March2015Saturday, at 12:55, Dave Temkin <dave@temk.in> wrote:

> Seems like an odd waste of resources; what if Google, Akamai, Netflix, =
and
> anyone else who wanted caches wanted IPs in that block? The IX would =
be out
> of address space pretty quickly, forcing a majority of users to =
re-number
> because of a small number of other users.
>=20
> -Dave
>=20
> On Thu, Mar 12, 2015 at 1:07 PM, Steven Schecter <schecter@gmail.com> =
wrote:
>=20
>> Those IPs appear to be used by to Google cache servers at the QIX.  =
It's
>> common for CDNs to utilize provider space and not maintain their own
>> layer-3.  E.g. cache servers connected to switch, connected to =
provider,
>> without the requirement of a router.
>>=20
>>=20
>> /Steve
>>=20
>> On Thu, Mar 12, 2015 at 3:58 PM, Jason Lixfeld <jason@lixfeld.ca> =
wrote:
>>=20
>>> So today, I saw this:
>>>=20
>>> BlackBox:~ jlixfeld$ host google.ca 8.8.8.8
>>> Using domain server:
>>> Name: 8.8.8.8
>>> Address: 8.8.8.8#53
>>> Aliases:
>>>=20
>>> google.ca has address 206.126.112.166
>>> google.ca has address 206.126.112.177
>>> google.ca has address 206.126.112.172
>>> google.ca has address 206.126.112.187
>>> google.ca has address 206.126.112.151
>>> google.ca has address 206.126.112.158
>>> google.ca has address 206.126.112.157
>>> google.ca has address 206.126.112.173
>>> google.ca has address 206.126.112.181
>>> google.ca has address 206.126.112.155
>>> google.ca has address 206.126.112.147
>>> google.ca has address 206.126.112.185
>>> google.ca has address 206.126.112.143
>>> google.ca has address 206.126.112.170
>>> google.ca has address 206.126.112.162
>>> google.ca has IPv6 address 2607:f8b0:4006:808::100f
>>> google.ca mail is handled by 50 alt4.aspmx.l.google.com.
>>> google.ca mail is handled by 30 alt2.aspmx.l.google.com.
>>> google.ca mail is handled by 20 alt1.aspmx.l.google.com.
>>> google.ca mail is handled by 10 aspmx.l.google.com.
>>> google.ca mail is handled by 40 alt3.aspmx.l.google.com.
>>> BlackBox:~ jlixfeld$
>>>=20
>>> That is not Google IPv4 address space, and those IPv4 IPs are not =
being
>>> announced by 15169.
>>>=20
>>> Am I dumb in thinking that this is weird or is this sort of thing
>>> commonplace?
>>=20
>>=20
>>=20
>>=20
>> --
>> Steven J. Schecter
>> (m) 917.676.1646
>>=20


home help back first fref pref prev next nref lref last post