Thanks Peter for the pointers.
There's a problem that tinydns and dnscache only listen on one ip on which
they are configured.
So on the real servers, I have IPs 10.0.0.2 and 10.0.0.3 assigned to the lo0
How will dns.monitor (Mon) running on the primary loadbalancer reach the
tinydns or dnscache service on the real servers?
In fact, I have two DNSCache VIPs in ldirectord.cf that are accessible from
all machines except the loadbalancer itself. Therefore, I cannot resolve from
This is because tinydns/dnscache will refuse to answer queries on any dest
address other than the one it is configured for. i.e. TinyDNS/DNSCache are
configured to listen on the vip, but will refuse to answer queries destined
the real ips.
There are patches for this, but it's also a production environment.
Quoting Peter Mueller <pmueller@xxxxxxxxxxxx>:
> > If the solution is not in ldirectord, can I run mon
> > simultaneously with the
> > dns.monitor script to alter the ldirectord/lvs table when a
> > DNS server stops
> > responding because of drive failures or whatever.
> There is probably some way in ldirectord, but since you said mon.. Here is
> a perl script that Wensong (?) wrote a long time ago in a land far, far away
> to monitor LVS through MON:
> You might have to change the -r to -R etc., minor cosmetic changes.
> > My goal is to at least keep the 2 DNSCache IP's loadbalanced
> > and highly-available as they are both used a lot.
> I think you need to find out why it is crashing and fix it. I don't like
> using LVS with DNS as DNS balances itself..
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.563 / Virus Database: 355 - Release Date: 1/17/2004
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users