DNS Load Balancing
kcd at daimlerchrysler.com
Fri Apr 7 22:28:22 UTC 2006
Um, has it occurred to you that all of those requests would be making
*everyone*else*'s nameservers work harder too? This isn't just about
your contractual relationship with your DNS hosting provider, it's also
about your relationship with the rest of the Internet community. You
would be basically mooching off the common resource pool -- possibly
even my company's resources -- just because you're too lazy to implement
real load balancing. That doesn't seem very fair or responsible, does it?
fritz-bayer at web.de wrote:
>I'm a java developer and I'm planning a java server application cluster
>with tomcat, which will HTTP requests on port 80.
>The most important thing is the load balancing, as only cluster can
>handle the heavy load, which we expect. That's why I would like to use
>DNS load balancing, as it's easy to set up.
>Because the application is only always used for an hour or more, but
>then very heavily and not all all at other times, the Time Alive has to
>be set to zero or maybe a minute, so that yo get fairly often a a new
>However, I have read that the problem with this might be, that you need
>more dns servers, because the load on the dns server increases heavily.
>Can somebody tell me how many connection requests would cause a load
>problem for a dns server? We are hosting dedicated servers at a big
>provider in germany, who is very reliable.
>So whats the maximum of connection requests per second?
More information about the bind-users