Originally Posted by Brian Conrad
Looks like the problem with my Sony S480 on Netflix and Amazon were due to the "Auto" which was probably using AT&T's DNS server and when manually configured to Google's 220.127.116.11 and 18.104.22.168 connects fine. I might have to see if the Samsung was using a AT&T or maybe a different DNS server.
If I understand correctly, you're talking about the player's network configuration.
Auto would likely mean using the DHCP specified name server. Your router is what is telling the player what it should use as a name server. Routers can be configured to override this value with one specified manually. By default though, it passes along the name server it was assigned via your ISP.
In order to choose the optimal node or farm of the CDN to connect to, you need to be using DNS that is aware of your location. Typically this means using the default name server as assigned by your ISP.
In other words, do nothing other than use the default values and you'll have the optimal configuration. Auto should acheive the best results.
If there is an exception to this I would be interested in hearing the details. Thanks!
Hmmm, i'm starting to wonder why DNS is being used for this. Wouldn't it be better for the netflix app to check for itself on a regular basis, which part of the CDN delivers the best performance. Using DNS for this seems like a kludge. Although maybe it is consistent enough that DNS is sufficient. (?)