Poor man's solution, since BIND doesnt know or care if a node is up (or if
it event exists):
Have a cron task running on the DNS server that runs http_ping.
http://freshmeat.net/projects/http_ping/?topic_id=90%2C152
Have it ping each webserver address/port, and check the return code. If it
fails, perform a dynamic update to DNS, to remove the address of the down
server/service from DNS. Have the cron task re-add the address when the
server/service comes back. You cant just "ping" the box with a normal ping,
as the system as a whole could be "up", but not the httpd listener. So,
something like http_ping would let you look specifically for the http
service.
I use the tool myself at home, to monitor my web cam server. If the web cam
server responds, the task updates a link on my home page, indicating cam
status. The same concept could be used to run an nsupdate against some
multi-homed entries in DNS.
Ken
-----Original Message-----
From: DARCY,MATTHEW (HP-UnitedKingdom,ex2) [mailto:matthew.darcy@xxxxxx]
Sent: Thursday, October 31, 2002 6:40 AM
To: 'bind9-users@xxxxxxx'
Subject: load balancing / round robin with bind - well sort of.
hi all,
I am reading sections of the oreilly bind9 books and surfing the web for
information on possible load balanced solutions with bind 9.
At the moment I have not found anything of interest. I would like to have
for example
1 website
the website replicated on 2 servers.
I would like web traffic to go to either site, if I turn of the webserver on
one site I would like traffic to ONLY go to the site that is turned on.
Has anyone done anything like this, is it possible (at the moment I think
not but I would be happy to be proved wrong) whats involved, does it work
well etc etc......
Discuss......
thanks,
Matt.
|
