Hello Everyone,
I'm experiencing an issue with DNS Resolution Timeouts browsing the web in our organization, they are very sporadic, and generally when you get the error, a refresh will bring the page up. Let me give you a little background:
Ee have an ASG525 appliance running 8.308, DHCP delivers IP, and DNS points to our Internal DNS server which handles our local intranet, forwarders are set to point to the internal IP of the astaro gateway, and also OpenDNS 220.220 and 222.222. Those same OpenDNS servers (in the same order) are set as DNS forwarders in astaro. I have even changed the DNS timeout on the Windows DNS server side from 3 to 4 seconds which seems to help a little but has not removed the problem entirely.
Generally things work just fine, but our help desk is getting calls about the DNS resolution timeouts (in both AD SSO and Transparent filtering profiles) and it seems like it just shouldn't be happening.
I have read the best practices as described on the board and really the only thing we're not doing that is recommended is to deliver the OpenDNS servers as secondary and tertiary DNS servers through DHCP. Currently DHCP delivers DNS pointing to three internal DNS servers, all set up to forward to Astaro, then OpenDNS.
Any help would be appreciated, thanks!
I'm experiencing an issue with DNS Resolution Timeouts browsing the web in our organization, they are very sporadic, and generally when you get the error, a refresh will bring the page up. Let me give you a little background:
Ee have an ASG525 appliance running 8.308, DHCP delivers IP, and DNS points to our Internal DNS server which handles our local intranet, forwarders are set to point to the internal IP of the astaro gateway, and also OpenDNS 220.220 and 222.222. Those same OpenDNS servers (in the same order) are set as DNS forwarders in astaro. I have even changed the DNS timeout on the Windows DNS server side from 3 to 4 seconds which seems to help a little but has not removed the problem entirely.
Generally things work just fine, but our help desk is getting calls about the DNS resolution timeouts (in both AD SSO and Transparent filtering profiles) and it seems like it just shouldn't be happening.
I have read the best practices as described on the board and really the only thing we're not doing that is recommended is to deliver the OpenDNS servers as secondary and tertiary DNS servers through DHCP. Currently DHCP delivers DNS pointing to three internal DNS servers, all set up to forward to Astaro, then OpenDNS.
Any help would be appreciated, thanks!