Currently we use explicit web proxy servers to handle browser traffic from our desktops. The proxy DNS name only returns a single IP when queried from DNS and we use topology records to keep user resolving the closest proxy server. With rising traffic demands we are looking to add additional proxy at one site. Has anyone experienced problems with DNS round robin for web proxy servers? I know the TCP session will stick to a proxy server until the session is torn down due to idle or other reason, but the next TCP session may get new IP resolution from DNS when TTL expires. I don't think the Internet facing IP of user sessions on these two proxy servers would be a huge concern for major websites.
No comments:
Post a Comment