ENS/NAT problem (DNS: unknown lookup)

[4Play]

Hello, I have been using wingate for quite a while now, but I never had any real issues with it...till now. The problem is that when any of the client linux machines on my network try to resolve a host like "download.unesp.br" for linux upgrades, the wingate server does it's job nicely and forwards the request. However, on a second attempt to resolve the same host, I got a "host could not be resolved" and Gatekeepr tells me "DNS: unknown lookup". But if instead of the domain name, I place the IP address (instead of download.unesp.br, I use 200.145.1.24) , it works for as many times as needed. But now I am in a situation where I can't place the IP address instead of the URL :( So does anyone have any idea on how to fix this??

p.s: interestingly, this only happens on Linux machines....so perhaps it's related to ENS?

-Wingate Server is a P3 1Ghz running WinXP Pro
-Clients with problems are RedHat9 Linux machine and a Debian Linux Machine

[adrien]

hmmmm

sounds like some bogus packets are being sent on port 53 UDP. If the linux machine is sending normal DNS query packets, we should be decoding them properly.

You don't have a packet capturing facility do you? If you could capture some of these DNS requests that choke WinGate like that, we should be able to quickly figure out what is going on.

The other option could be to disable the cache in the DNS resolver settings in WinGate.

Adrien

[4Play]

Thanks for the reply!!!

I don't have a packet capturing facility, but I am obtaining one...( a bit of googling brought me to Sniff'em ) so Ill have that in a bit.

Also, I just disabled the DNS catching (I should have though of that :P) and will test it later (1am now)

I'll post back here as soon as I get the new results :)

Thanks very much

**update**
Disabling the DNS catch solved the problem....still gonna take a look at the packets tho ;)