On Sun, Apr 16, 2017 at 04:20:20PM +0300, Max Tulyev wrote:
> got the same from Kiev, Ukraine:
>
> dig fbcdn.com
> fbcdn.com.300 IN A 31.13.74.1
> which is slow and routed through USA
>
> and
> dig fbcdn.com @8.8.8.8
> fbcdn.com.299 IN A 31.13
Hi,
got the same from Kiev, Ukraine:
dig fbcdn.com
fbcdn.com. 300 IN A 31.13.74.1
which is slow and routed through USA
and
dig fbcdn.com @8.8.8.8
fbcdn.com. 299 IN A 31.13.93.3
which is fast and routed through Germany
Same is for IPv6.
Is
On Wed, Mar 22, 2017, at 12:25, Mike Hammett wrote:
> Are your DNS resolvers on your network? No DNS forwarding?
Yes, DNS resolvers on our network. Forwarding only for facebook.com and
fbcdn.com, in order to eliminate bad performance associated with "direct
recursion".
Hi Mike,
Im running some DNS on my own for a few hundred users from an private
community project. But this issue is also affecting DNS from smaller/other
ISPs which do NOT use any forwarder but the root DNS.
Best regards
Jürgen
quot; ,
nanog@nanog.org
Sent: Wednesday, March 22, 2017 5:02:12 AM
Subject: Re: Facebook more specific via Level3 ?
On Tue, Mar 21, 2017, at 20:38, Jürgen Jaritsch wrote:
> I understand that FB is using some type of DNS geo-loadbalancing and other
> mechanism to redirect users to (possi
Von: Radu-Adrian Feurdean [mailto:na...@radu-adrian.feurdean.net]
Gesendet: Mittwoch, 22. März 2017 11:02
An: Jürgen Jaritsch ; Doug Porter ;
nanog@nanog.org
Betreff: Re: Facebook more specific via Level3 ?
On Tue, Mar 21, 2017, at 20:38, Jürgen Jaritsch wrote:
> I understand that FB i
On Tue, Mar 21, 2017, at 20:38, Jürgen Jaritsch wrote:
> I understand that FB is using some type of DNS geo-loadbalancing and other
> mechanism to redirect users to (possibly) nearer mirrors. The used DNS is
> directly requesting the root DNS and not any other public DNS (e.g. not
> 8.8.8.8). Runn
> looks like this is also affecting other prefixes:
Many of our prefixes are only announced to peers in the metro
they originate in. Please stop obsessing about this detail; it's
not the problem.
> I understand that FB is using some type of DNS
> geo-loadbalancing and other mechanism to redirect
guill...@reservetele.com]
Gesendet: Dienstag, 21. März 2017 20:38
An: Jürgen Jaritsch ; nanog@nanog.org
Betreff: RE: Facebook more specific via Level3 ?
Are they replying with that subnet via dns when requests are being made?
Luke Guillory
Network Operations Manager
Tel:985.536.121
, March 21, 2017 2:24 PM
To: nanog@nanog.org
Subject: Re: Facebook more specific via Level3 ?
Hi,
> This specific, and many others, are only announced to peers in the
> metro they originate in. To receive this prefix directly you'll need
> to peer with us in Los Angeles.
the point
6.0 3.1
Best regards
Jürgen
-Ursprüngliche Nachricht-
Von: Doug Porter [mailto:d...@fb.com]
Gesendet: Dienstag, 21. März 2017 18:41
An: Jürgen Jaritsch ; nanog@nanog.org
Betreff: Re: Facebook more specific via Level3 ?
> 31.13.70.0/24
>
> This more specific is only vis
Hi,
> This specific, and many others, are only announced to peers in the
> metro they originate in. To receive this prefix directly you'll
> need to peer with us in Los Angeles.
the point is: Level3 is exporting this prefix to the EU since ~1 week
Telia is learning it from Level3 and they also
> 31.13.70.0/24
>
> This more specific is only visible via AS3356 ... Facebook
> isn’t even announcing it via direct peering.
This specific, and many others, are only announced to peers in the
metro they originate in. To receive this prefix directly you'll
need to peer with us in Los Angeles.
It
I see that specific route both of my upstreams and not going through level
3.
NetworkNext HopMEDLocPrf Weight Path
*>x 31.13.70.0/24 x.x.x.x 0 80 0 6461 32934 i
*i 31.13.70.0/24 x.x.x.x 0 80 0 209 32934 i
* 31
Hi,
is anyone else receiving Facebooks /24 more specific from Level3 (AS3356)?
31.13.70.0/24 *[BGP/170] 1w5d 17:21:28, MED 0, localpref 100, from
a.b.c.d
AS path: 3356 32934 I, validation-state: unverified
This more specific is only visible via AS3356
Face
15 matches
Mail list logo
