Two issues I have with your statement:
- Each OpenDNS server is delivering a different address for netflix-822.vo.llnwd.net (go to http://www.opendns.com/support/cache/ and request a cache check for netflix-822.vo.llnwd.net and notice that the IP addresses returned for the five sites US sites are all different), and
- Depending on which address one gets, it will affect the distance the packets will have to travel because it is likely giving you the address of the closest server to the particular DNS Server than the closest address to one's Roku box.
You're right. That does seem to be the case. They're using the polling DNS for geolocation purposes, which is perfectly fine when you're using your local ISP's DNS.
It's not that
much worse with OpenDNS since with that system, you're still hitting the closest DNS to your physical location. But, as you said, the closest Netflix datacenter to that DNS location and the closest one to you may or may not be one in the same.
I'm in Houston and apparently I hit the Chicago OpenDNS server, which sends me to the Dallas Netflix center. So things are rosy on my end, but your mileage may vary.
Now, unless there's more load balancing going on behind the scenes at Netflix's end, this is bound to create congestion problems. If your nearest datacenter is already overloaded, but it insists on sending you there anyways, you're worse off than if they sent you to the center across the country from you. If this is how it's working and what's causing people all sorts of problems, then it's because Netflix underestimated future demand in some areas when designing the system and dug themselves into a hole.