etresoft wrote:
DNS issues will affect domain name lookups.
Yes I know that, why some see a faster speed because the alternate DNS is not as overworked as the ISP DNS.
In any event, DNS will have zero effect on downloads.
That's where your mistaken.
Many Content Delivery Networks don't use Anycast or not yet supporting the edns-client-subnet extension created by Google so that CDN requested content downloads are from the closest server to the user.
CDN's that don't use AnyCast or eden-client subnet extension are using the location of the DNS server itself as the closest point to initiate downloads, which are in a lot of cases not as close to the user as possible like the ISP DNS server is.
OpenDNS does not have servers everywhere, only in major cities because they are focused not on providing DNS everywhere like GoogleDNS almost does, rather on DNS level content filtering for profit.
So as a remedy the alternate DNS and the ISP server need to be located in the same general vicinity or else there is a reduction, even very serious reduction in CDN content delivery time, including OS X reinstalls, which is slow enough as it is.
Without any location verification with the user being recommended such action, it could be causing more harm than good, especially if they have to reinstall their OS from Akamai.
I don't have a problem with the recommendation as long as it's going to work properly for that user.
All you have to do is delete the DNS entries and the values will automatically revert back to whatever your ISP provides.
What about the network settings saved in NVRAM?
If the user command r boots into Recovery and attempts to reinstall OS X because they can't boot from it and it's too slow to reinstall so then what?
Not everyone has whipping fast 20 Gbps, some only have 5 or so and data caps.
What if some guy in India who speaks Engish enters OpenDNS into their machine and it works somewhat well until they can't download something because it's coming from a Akamai server in London?
See the problem?
