Some users may find a network blocking DNS request or filtering results. A work around this is to use port 80 request. Port 80 commonly used for HTTP or web request is the best workaround. A port 80 client resides on the users PC, the user sets the PC to query the resident client, the client does a HTTP request to a remote HTTP enabled DNS server. The client then returns the IP address to the users PC DNS socket.
In this FAQ we show how to use the AdaptorConfig client to do port 80 request from the Open-DNS.org (not opendns.org) site. At Open-DNS.org exist the query page located at query.Open-DNS.org where it will returned a resolved IP address for any valid domain.
To use the AdaptorConfig client as a work around to port 53 TCP/IP-UDP blocking.
How this works: For this example we will use "sampledomain.com" as the query.
The AdaptorConfig client is designed for a single PC, if you want to run several PC's off a Port 80 Resolver, install the WTSSoftware application WindowsDNSServer.exe from WindowsDNSServer.com and use it as your DNS Server.
Note that on initial setup any Port 80 resolver will be initially slower on resolve times until the resolver has cached the queries that you are using on your system. This is due to the fact that a port 80 resolver has about 2 more hops to go through before sending back the IP address. However once it has cached the query's it will respond much faster. In the case of WTSSoftware DNS products, the resolver will refresh the expiring TTL cache entries prior to the expiration, thus any subsequent query's will have immediate results, which in turn may be faster than if a client was querying a public DNS server.