DNS still has problems

[DBeard]

DNS look up is still very slow through Wingate 5.2.2
The longer the server is up between reboots, the slower it gets.
Still having many dropped sockets and DNS look up failures.

Connecting directly to the gateway w/out the proxy AND running a different proxy software both does not experience this problem.

Hoping you've tackled the DNS issues and dropped sockets in the next release. Is there a next release coming soon? And have you addressed any of these problems?

Thanks

[Pascal]

DNS look up is still very slow through Wingate 5.2.2
The longer the server is up between reboots, the slower it gets.
Still having many dropped sockets and DNS look up failures.

Been chatting to the guy who did most of the work on the DNS system. There are no real conclusive reasons for it to be slow / slow down like that. A few ideas came up though:

1. Try turning off all logging for DNS. DNS is probably the heaviest user of logging, especially if debug logging is turned on. As this is mostly disk-based activity, it could be slowing the process down more than is necessary.

2. Can you post some information about the cache settings / etc. in the DNS/WINS resolver ?

3. When it gets to the slow-down point, is there anything abnormal about the WinGate Service itself ? Is it using excessive memory / handles / etc. ? (You can normally see this through Task Manager, although ProcessViewer from www.SysInternals.com is a useful way to view this as well)

[DBeard]

hmm, I'll turn off logging on DNS, see if that helps.

I've tried different settings as far as DNS cache goes. For now, I am not caching, because I have had a problem with the wrong director being cached and forever forwarding to the wrong location. So I purged and disabled for now.

Next slow down I'll try to decern some of the information you request and post here.

Thanks

[Pascal]

Next slow down I'll try to decern some of the information you request and post here.

Thanks. It might be worth specifying the DNS Servers you use in the DNS/WINS resolver as well, if you haven't done that already. That tends to improve the performance marginally (And has resolved similar problems before)