DNS slow / very slow - sometime failed ...

[sigih.]

Hello All,

I have a problem on my wingate server:
2008R2 with 2 NICs.
192.168.0.x for internal net ant 87.24x.x.x for external +Internet.
On the external there is a cable modem - my IP is registered + a domain on it.
I run also a webserver + certain other things.
From the Internet there is not problem to reach all my services ...
But form the servers internal nic it's near impossible to reach the internet cause of extrem bad DNS from the server.
I have a fixed IP on the external nic + Gateway + the 2 DNS Servers from my provider.
Clients connetion also works without a problem via wingate!

The mailserver is on the server on the internal nic and has lots of connection errors like
... :110': Network communication error (0) OR
... s.com:25 (The connection has been dropped because of a network failure or because the peer system failed to respond.)) for ...

The internal nic is configured:
IP: 192.168.0.1
Mask: 255.255.255.0
Gateway: none
DNS1: 192.168.0.1 - there wingate runs
DNS2: none

My mailserver (Hexamail) has only the possibility to give the name of the providers external mailserver or the IP address of the external mailserver.
Both are not working correct - Also with mail.X.com or IP - nope ! Same problems.

Do I have a configuration failure in wingate?
Has anyone a idea what could wrong why on the server itself there is so bad DNS ... ?

regards
sigih.

[adrien]

Hi

Which version of WinGate is this?

6 vs 7 have very different DNS capabilities. If you're running WinGate 6, you'll have a DNS loop by pointing the WinGate computer at itself for DNS.

Are you on a active directory?

Regards

Adrien

[sigih.]

Hello Adrien,

I have 7.3.0.3506 but the problems were also with older builds.
Yes I've a DNS loop - see screenshot.
... and no I'm not in an AD - I have no AD active on the server.

Sigi-0000.png (36.77 KiB) Viewed 4269 times

regards
sigih.

[adrien]

Hi

ok, I don't think it's anything to do with 192.168.0.1 then. The OS will use it, but WinGate won't (since it's not good to talk to yourself when you're a DNS server).

Therefore the problem must lie with the other 2 DNS servers.

For expediency, in the cases where the ISP DNS servers aren't very good, we normally recommend adding a google DNS server (8.8.8.8).

If you enable debug logging in the DNS client, you should be able to see whether requests to either or both of those servers are timing out / retrying too much.

Regards

Adrien