
February 4th, 2002, 05:49 AM
|
|
Contributing User
|
|
Join Date: Jan 2002
Posts: 409
Time spent in forums: < 1 sec
Reputation Power: 7
|
|
What software are you all using for node failover?
Right now we are looking at using rsync and Understudy as a means of mirroring our primary server to a slave at a remote location. This seems an acceptable solution. However, Understudy depends on BIND. And freebsd has pointed out that TinyDNS is a better DNS server over BIND. Understudy carries a price tag with it, while TinyDNS is free.
freebsd,
I know you prefer TinyDNS to BIND. TinyDNS supports failover, but it needs an external program to edit its files. Any recommendations?
Quote:
How do I direct traffic away from a dead server? If one of my servers dies, I want tinydns to stop providing that server's IP address, so clients won't waste time trying that server.
Answer: The following answer is for versions 1.04 and above.
tinydns is designed to work with external programs that monitor the health of your servers. Specify each address as an alias with a 5-second TTL:
+www.heaven.af.mil:1.2.3.150:5
+www.heaven.af.mil:1.2.3.151:5
+www.heaven.af.mil:1.2.3.152:5
An external program can remove an alias by simply changing + to - on the relevant line, then running make. Later, when that server has recovered, the program can change - back to +.
Note that standard client behavior is to try each of the addresses provided by tinydns, so a server outage will merely produce delays, not failures. To minimize the delay, smart clients will try each address with a two-second timeout before retrying each address with a long timeout. |
http://cr.yp.to/djbdns/faq/tinydns.html#dead-server
|