by adrien » Nov 26 13 9:27 am
Hi
normally WinGAte DNS client (which is what is reporting that error you are seeing) uses the DNS servers that are used by the OS that WinGate is installed on.
It also probes them, which involves sending a couple of requests to each known server. This is used to check for DNS looping, and to test whether the DNS server is able to forward requests to a DNS server on the internet.
So that error will be reported if no known servers (e.g. discovered from the host OS, or manually entered by you) passed the test for being usable for internet lookups.
So there are several reasons this can occur:
1. The host OS doesn't have suitable DNS servers entered into the network adapter TCP IP properties
2. The DNS servers that the WinGAte computer are configured to use do not have any forwarders set, so do not pass requests onto internet servers
3. The DNS client in WinGate has disabled probing for or disabled internet lookups for servers (unlikely unless you set this yourself).
if the reason is 1 or 2, then I would expect that the host WinGate computer does not have access to the internet - e.g. if you open a web browser on that computer, it can't find anything either.
Depending on your network setup, what to do next can be quite different.
e.g.
a) if WinGate is the sole internet gateway, and you're not running any other DNS servers, then you will need to enter your ISP DNS server IP address into your external adapter TCP/IP properties.
b) if you have a DNS server on your LAN, it needs to be configured with forwarders so it can forward requests it isn't authoritative for. It can forward to WinGate or some other server (e.g. ISP DNS server). If it forwards to WinGate, then WinGate needs to know about the ISP DNS server
Adrien