Jump to content
WAPT Forum
Sign in to follow this  
Guest rpillen

Load agent is caching DNS

Recommended Posts

Guest rpillen

To explain our problem, we first need to explain the setup we're using.

 

We got a SharePoint farm (2 WFE's, 2 Application Servers, 1 SQL server) with ISA 2006 as Reverse Proxy. Running stress tests gave us insight in that our ISA server wasn't sufficient for our load (up to 900 users), so we decided to setup a second ISA server and let 3DNS balance the load over the 2 ISA servers. (30 seconds intervals)

 

While our requests from our client were referenced to the right ISA machines (swiched every 30 seconds), all requests from the load-test were pointed to the same ISA machine. Even in a new load-test, they were still pointed to the sole ISA machine. After restarting the WAPT Agent, the requests were sent to the other machine, but then the first machine didn't receive requests anymore.

 

We can't continually restart the Load agent on every swap of our 3DNS.

I think the Load agent caches the DNS and just sends requests to IP-addresses. In our setup with 3DNS load balancing that is not sufficient.

Please look into it.

 

Thanks in advance

R. Pillen

Share this post


Link to post
Share on other sites
Guest angela
To explain our problem, we first need to explain the setup we're using.

 

We got a SharePoint farm (2 WFE's, 2 Application Servers, 1 SQL server) with ISA 2006 as Reverse Proxy. Running stress tests gave us insight in that our ISA server wasn't sufficient for our load (up to 900 users), so we decided to setup a second ISA server and let 3DNS balance the load over the 2 ISA servers. (30 seconds intervals)

 

While our requests from our client were referenced to the right ISA machines (swiched every 30 seconds), all requests from the load-test were pointed to the same ISA machine. Even in a new load-test, they were still pointed to the sole ISA machine. After restarting the WAPT Agent, the requests were sent to the other machine, but then the first machine didn't receive requests anymore.

 

We can't continually restart the Load agent on every swap of our 3DNS.

I think the Load agent caches the DNS and just sends requests to IP-addresses. In our setup with 3DNS load balancing that is not sufficient.

Please look into it.

 

Thanks in advance

R. Pillen

 

Hello,

 

We are going to implement the option which will allow enabling\disabling DNS caching. It will be implemented in our newer version.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×