News for hackers. Stuff that matters.

A comment on Verizon Throttles Netflix Subscribers in Test It Doesn't Inform Customers About. Parent comment

Re:Verizon Throttles Netflix Subscribers in Test It Doesn't ... by jlgaddis on Monday July 24, 2017 @01:30PM (#14840622)
Let's say you live in NYC but you're using a DNS server (resolver) in Seattle. When your client performs a DNS query, you may get a response that directs you to a server/CDN/whatever in or near Seattle as opposed to one closer to you in NYC. Then, the data (streaming video) is traversing the country to get to you, passing through many more (potentially congested) interconnects/links on the way.

Reality is a bit more complicated than this simple example but such an issue is certainly not unheard of (and inspired mitigations such as RFC7871, for example).

[ Parent | on HN ]
Re:Verizon Throttles Netflix Subscribers in Test It Doesn't ... by JshWright on Monday July 24, 2017 @01:55PM (#14840911)
Both Google and OpenDNS use anycast addresses for their DNS servers that are very likely to route though a 'local' server. I think ISP games are far more likely to be the root cause here...
[ Parent | on HN ]
Re:Verizon Throttles Netflix Subscribers in Test It Doesn't ... by notyourday on Monday July 24, 2017 @03:11PM (#14841662)
Google DNS requests enter Google network in multiple places. DNS itself is not served from the edges.
[ Parent | on HN ]