On Tue, Sep 04, 2012 at 03:08:10PM -0600, Pete Ashdown wrote: > I'm trying to setup a DNS LVS like this:
There's a few ways to do this, but we have it setup like this: -A -t test-virt.ns.sr.sonic.net:mdns -s rr -a -t test-virt.ns.sr.sonic.net:mdns -r b.ns.sr.sonic.net:domain -g -w 1 -a -t test-virt.ns.sr.sonic.net:mdns -r a.ns.sr.sonic.net:domain -g -w 1 -A -u test-virt.ns.sr.sonic.net:mdns -s rr -a -u test-virt.ns.sr.sonic.net:mdns -r b.ns.sr.sonic.net:domain -g -w 1 -a -u test-virt.ns.sr.sonic.net:mdns -r a.ns.sr.sonic.net:domain -g -w 1 -A -u ns1.sonic.net:domain -s rr -a -u ns1.sonic.net:domain -r b.ns.sr.sonic.net:domain -g -w 1 -a -u ns1.sonic.net:domain -r a.ns.sr.sonic.net:domain -g -w 1 -A -t ns1.sonic.net:domain -s rr -a -t ns1.sonic.net:domain -r b.ns.sr.sonic.net:domain -g -w 1 -a -t ns1.sonic.net:domain -r a.ns.sr.sonic.net:domain -g -w 1 The real servers must be configured to listen to the virtual IP address(es) as well. The test virt is in place since we have several of these name server pods anycasted in our network and we need a virtual server specific to each pod so we can monitor the pods. If I were to set this up again, I'd probably use ipip tunneling instead of direct routing to eliminate the need for the hosts to be in the same network segment. The LVS box would get uplinks to a pair of routers, receive default via BGP and announce the virtuals and a loopback for management. The real servers could be configured the same way or just just a single uplink to different switches. -- Kelsey Cummings - k...@corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407 _______________________________________________ Please read the documentation before posting - it's available at: http://www.linuxvirtualserver.org/ LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org Send requests to lvs-users-requ...@linuxvirtualserver.org or go to http://lists.graemef.net/mailman/listinfo/lvs-users
