Fastly is suboptimal when using Google DNS

Follow

rlx01

• June 29, 2016 23:12

Hi,

Ever since the switch to the Fastly run DNS (fastlylb.net), Google DNS using clients are being redirected to suboptimal POPs.

I end up somewhere in Chicago when I’m based in SF.

Looks like the Fastly servers don’t support EDNS0.

0

• 

  Justin

  • June 30, 2016 12:45

  Hi

  If you send in the text block you get from visiting https://www.fastly-debug.com/ to support@fastly.com. It'll help us to investigate and take action.

  Thanks

  0

  Permalink
• 

  Håkon Erichsen

  • October 11, 2016 00:50

  Google DNS + Bay area + Fastly seems like it's not working that well: Our office traffic to our CDN constantly gets routed to SEA or LAX instead of SJC. While the bay area in no way represents all of our customers, it's annoying as it slows down our content in our own office.

  0

  Permalink
• 

  Mark Teodoro

  • January 17, 2017 20:38

  We recently started returning anycast answers for queries from public resolvers like OpenDNS and Google Public DNS. This should result in better performance for users coming through those resolvers. We're also working on EDNS Client Subnet support which will help as well.

  0

  Permalink

Please sign in to leave a comment.