Accessing Websense Active/Active Proxy Config using Windows DNS Round Robin fails to send proper block messages
Hello,
I am incorporating an active/active cluster from Websense. Users point to an fqdn that has 2 virtual ip addresses that provide automatic fail over if one of the devices goes offline.
FireFox appears to do a dns lookup of the proxy as soon as one tries to get to a website. The problem is with blocked sites. Namely the proxy is trying to respond for a "gambling" or other reason. Due to the DNS lookup, Websense appliances along with DNS Round Robin appear to be splitting the building of the page. This causes the block message to show up as "private IP" address rather than simply showing the reason for the block (i.e. Gambling).
These devices are running Linux and are IP based only as they hit Websense. They are not part of a domain.
By the way, Windows clients in a domain using Internet Explorer do not have this problem. My dilemma is that we have 90% of our clients running Linux, thus we cannot take advantage of load balancing.
Any ideas of how to prevent all of the DNS lookups. Note that I avoided using a proxy.pac as I am simply trying to get things to work. I am using explicit proxy, pointing to an fqdn.
Thanks very much.
所有回复 (1)
Far beyond the scope of Firefox end-user support.
Please see the developer support page: Where to go for developer support
Or post to the Mozilla Developer Network's Stack Overflow page