dns resolver not resolving from local dns servers

[vikingivesterled]

The dns resolver will not resolve from dns servers (2, both local on the 10.1 network, within same mask as wingate's own internal ip address) entered into servers network configuration. Not either if I add them specifically as dns servers under the dns resolver.

If I add a 3'rd dns server (not same mask) to the dns resolver, it starts resolving.

This is very inconvenient since I need it to resolve some web sites to the internal address for acessing locally, and this is done of my own dns servers.
It is also needed that both the server itself and the Wingate dns resolver can resolve names.

Wingate version 6.0.4 build 1025
License 5.x pro unlimited

[Pascal]

Have you enabled debug logging for the DNS/WINS Resolver and had a look in the log file to see what the potential problems could be?

That should be your first step, because it will give us an idea of what causes the problem.

[dominic279]

My Problem is : DNS: Unknown lookup "something.com." <<<< This is a message from Activity ?

- My Wingate Server has ip : 192.168.1.2 - 255.255.255.0

- My Client :
+ Ip : 192.168.1.10 - 255.255.255.0
+ Gateway : 192.168.1.2
+ DNS: 192.168.1.2

When I use Wingate as DNS Server, Domain Names are resolved slowly.

HELP!