James Knott wrote:
On 04/07/2015 04:02 PM, Per Jessen wrote:
Now, how does incoming traffic get balanced? In my setup, with round-robin DNS.
How does DNS have anything to do with it? DNS is used to look up IP addresses.
Correct. Inbound traffic is destined for a <service>. <service>.example.com is configured with two or more IP addresses, each belonging to one of the inbound paths.
Are you saying that you have a DNS server configured to hand out different IP addresses for each access to your site?
Correct. It's perfectly normal - see named.conf::rrset-order. Think any high-availability N+1 setup. Also, see getaddrinfo() and /etc/gai.conf for info on how IP addresses are returned (un)sorted.
While that sort of thing is used by large servers, such as Google (anycast), I really don't see much need for small users.
Nor me, nor is multipath much needed by small users. I did say my comment was slightly off-topic.
Also, with large servers, such as Google, it's used to balance geographically, not just what link is used to a single site. There are also load balancers that distribute incoming traffic, but again that has to be done at some other point, if you want multiple routes.
For internal load balancing over multiple servers, we use LVS.
For example, you might use a routing protocol, such as OSPF or EIGRP to load balance incoming traffic and a first hop redundancy protocol, such as GLBP, to balance over mulitple routers for outgoing. Etherway, you need something to load balance incoming and outgoing traffic.
Well, in my business, for inbound traffic I use DNS round-robin, for outbound traffic I use a simple 'ip route nexthop' setup. -- Per Jessen, Zürich (1.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org