|
Before selecting round robin consider the drawbacks - a DNS server being down, DNS server inconsistency, an application expecting some kind of stateful interaction. Finding root cause with DNS round robin can be challenging. I'm not saying don't use it,
your situation may be able to mitigate/eliminate issues. just do so fully aware of the implications.
Thanks Warren.
I am looking DNS RR distribution. (DNS Round Robin Load distribution).
Round robin DNS is often used to load balance requests between a number of Web
servers. For example, a company has one domain name and three identical copies of the same web site residing on three servers with three different IP addresses. When one user accesses the home page it
will be sent to the first IP address. The second user who accesses the home page will be sent to the next IP address, and the third user will be sent to the third IP address. In each case, once the IP address is given out, it goes to the end of the list. The
fourth user, therefore, will be sent to the first IP address, and so forth.
Rgds
Simon
Harriscomputer
|
TThis message has been sent on behalf of a company that is part of the Harris Operating Group of Constellation Software Inc. These companies are listed
here.
If you prefer not to be contacted by Harris Operating Group
please notify us.
This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If
you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.
|
|
On Tue, Sep 18, 2018 at 1:22 PM Warren Kumari < [email protected]> wrote:
Hi,
Are we support load balancing with latest DNSSEC ? I have a DNSSEC application with unbound library. Do i have to add any extra configuration to support Load Balancing?
Your question is sufficiently light on detail that it cannot be realistically answered.
What sort of load balancing?
1: Traditional SLB - you hand out one IP address, and have a load balancer widget which shares this to multiple backends?
2: Global SLB - you hand out different IP addresses to different clients?
3: Round Robin - you hand out different IP addresses, but randomly / in a order, not tied to specific clients?
4: Anycast - you hand out the same IP address, but this lives on multiple sites, and routing takes care of getting people to the closest site?
5: Multiple nameservers? Something else?
The term "load balance" is very vague / can be applied to multiple things - for all of the above except #2, this should just work without any changes. GSLB *may* require more work, but may not.
# 5 is sufficiently undefined that it cannot really be answered :-)
What *exactly* is the question / scenario you are asking?
W
_______________________________________________
Please visit
https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
--
I don't think the execution is relevant when it was obviously a bad idea in the first place.
This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants.
---maf
|
