Knowledgebase: WinGate 6
Posted by Adrien de Croy (Import) on 13 December 2005 04:21 PM
If you are running an Active Directory and your WinGate server is on a machine other than the Active Directory Domain Controller/DNS server, you'll need to edit this menu.
When your WinGate server is a member of an Active Directory domain you will need to enter the IP address of your DNS server in the LAN adapter on the WinGate machine. This allows the WinGate server to log on to the domain but can cause a problem when the WinGate server receives a DNS resolution request from the network.
When the AD DNS server receives a DNS request it checks the upstream DNS server for resolution. If WinGate is the gateway server for the network then the AD DNS server will send WinGate the DNS request. When the WinGate server receives the DNS request it will check it's local adapter DNS settings and forward the request to the DNS server. Because the AD DNS server is listed in the DNS server settings on the local adapter you can end up with a DNS loop. Entering the IP address of the AD DNS server in the Advanced Options tells WinGate not to check that server and prevents the loop.
You'll know this is happening if you see a large amount of DNS requests in the activity screen in GateKeeper. You'll also find that internet access slows down and eventually stops if the DNS is looping.
If you have any questions about this article please contact Qbik Support.