DNS
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
User Name:
Password:
Remember me
Go Back   Dev Shed ForumsSystem AdministrationDNS

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread Dev Shed Forums Sponsor:
Stay one step ahead of the competition. Evaluate and give feedback on some of the hottest web development tools on the market today. Make your opinion heard! Click Here
  #1  
Old February 4th, 2002, 05:49 AM
Ted Striker Ted Striker is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Jan 2002
Posts: 409 Ted Striker User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 7
Question 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

Reply With Quote
  #2  
Old February 4th, 2002, 06:36 AM
freebsd freebsd is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Jan 2001
Posts: 5 freebsd User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 0
>> but it needs an external program to edit its files. Any recommendations?

1) By hand
2) Write a script ( Parsing the zone data format of Tinydns is relatively simple. So it'd take someone with 1 month of programming knowledge to write such a script)
3) Go to http://www.djbdns.org and search for twa web-based tool. Note, you need to install python binary (not mod_python).

Reply With Quote
  #3  
Old February 4th, 2002, 07:23 AM
Ted Striker Ted Striker is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Jan 2002
Posts: 409 Ted Striker User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 7
Thumbs up thanks freebsd

Man freebsd you are fast! Thanks. I'll check out that link.

I also found an example script while searching on this same topic:

http://www.ntlug.org/pipermail/disc...312/005677.html

Quote:
One way to set this up would be like this:

ISP1
Webserver
DNS server
Etc.

ISP2
Webserver
DNS server
Etc.

Use http://cr.yp.to/djbdns.html for your DNS server; has built in
DNS load balancing/failover stuff, sophisticated enough that all you should need to write a simple script like the following:

#!/bin/sh

cd /service/tinydns

while true ; do
ping -c1 theotherwebserver 2>&1 > /dev/null
if [ "$?" != "0" ] ; then
cp -f data.down data
make > /dev/null
else
cp -f data.up data
make > /dev/null
fi
sleep 15s
done


You'll have the files data.up and data.down created before hand,
with the .down file having the second server removed, and the .up file having both webservers listed.

You can run the script at any interval you want (every 15 seconds
as written above), and when one box can't reach the other for any reason, it removes it from it's DNS tables. As soon as it comes back up, it re-adds it.

Now, PLEASE note, that my script above is most likely NOT what you want to write (although it should work), it's just an example showing the logic. More likely you'll want to use something like "wget -q http://theotherwebserver/index.html" to verify that the other end is actually serving webpages, and not just responding to ping's, or maybe get even more elegant and use a small C or Perl program to do this.

Reply With Quote
  #4  
Old February 4th, 2002, 07:45 AM
freebsd freebsd is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Jan 2001
Posts: 5 freebsd User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 0
That logic could do the trick nicely in the event of any failure on the slave. If you think twice, the slave DNS server shouldn't be down that often, especially when it's supervised. It'd be a serious problem if supervise can't be restarted automatically. As a precaution, though that's necessary.

Reply With Quote
Reply

Viewing: Dev Shed ForumsSystem AdministrationDNS > What software are you all using for node failover?


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump

 Free IT White Papers!
 
Accelerating Trading Partner Performance
One in five. That's how many partner transactions have at least one error. That is an amazing statistic, particularly given the extraordinary leaps in innovation across the global supply chain during the past two decades. Download this white paper to learn more.

 
Competing on Analytics
This Tech Analysis is designed to help identify characteristics shared by analytics competitors, and includes information about 32 organizations that have made a commitment to quantitative, fact-based analysis.

 
Cost Effective Scaling with Virtualization and Coyote Point Systems
An overview of the industry trend toward virtualization, how server consolidation has increased the importance of application uptime and the steps being taken to integrate load balancing technology with virtualized servers.

 
Five Checkpoints to Implementing IP Telephony
Implementation planning for IP PBX software and IP telephony has become vital as businesses replace discontinued legacy PBX phone systems. This informative whitepaper outlines five "checkpoints" for any implementation plan that will help make IP communications a successful proposition.

 
Hosted Email Security: Staying Ahead of New Threats
In the last two years, email has become a fierce battleground between the nefarious forces of spam and malware, and the heroes of messaging protection. The spam volumes increased alarmingly every month, bringing clever new forms of phishing and virus propagation attacks.

 

Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 5 hosted by Hostway