it's a case of everything gets routed through "OpenDNS" ?
That's not quite how it works.
- Your system knows the IP address of a DNS (perhaps OpenDNS's)
- You enter a host name (e.g., "www.donationcoder.com") into your browser
- Your PC doesn't know the IP address of that server, so it asks the DNS (you can do the same thing manually via the nslookup command)
- The DNS looks it up in its database (maybe asking an upstream provider for help), and returns the IP address (in this case, 220.127.116.11)
- Your browser then sends an HTTP request to the IP address that it just got
So you can see that the DNS is only returning an address, not acting as a go-between for you and the server.
(And there are multiple layers below this, including TCP and UDP, and routing with IP addresses and MAC addresses, but that just clouds this question)
So when Mouser says that OpenDNS is having the problem, he (presumably) means that the route that the network chooses to get from his PC to the DC server has the same problem as the route from his PC to the OpenDNS server. Presumably they both pass through the same router at some point, and that router is illin'.