Hi, > (query facebook.com and fbcdn.com on 8.8.8.8 instead of regular recursive > resolving) and we get directed to Frankfurt or Amsterdam (never London or > Paris).
This is exactly what I've implemented yesterday on my end :). Best regards Jürgen -----Ursprüngliche Nachricht----- Von: Radu-Adrian Feurdean [mailto:na...@radu-adrian.feurdean.net] Gesendet: Mittwoch, 22. März 2017 11:02 An: Jürgen Jaritsch <juer...@jaritsch.at>; Doug Porter <d...@fb.com>; 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 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). Running some requests within 3 minutes gives > me the below > results: > > www.facebook.com => star-mini.c10r.facebook.com. => 31.13.77.36 > www.facebook.com => star-mini.c10r.facebook.com. => 157.240.2.35 > www.facebook.com => star-mini.c10r.facebook.com. => 31.13.93.36 > www.facebook.com => star-mini.c10r.facebook.com. => 31.13.76.68 Hi, the load-balancing definitely doesn't choose the *nearest* mirror. We are in France and unless we do dirty tricks, we *always* get directed to US sites (as far as LA), with horrible performance. Everything since end of December. As a consequence we let the dirty tricks in place (query facebook.com and fbcdn.com on 8.8.8.8 instead of regular recursive resolving) and we get directed to Frankfurt or Amsterdam (never London or Paris).
