While I would never recommend running a hosting op this way without appropriate bandwidth/power redundancy and security, we used to run our office similar to this. There's two possibilities that we tried at various times that might work for you, depending on your budget:
1. The cheap solution: Set up an additional NS server record on all hosted domains that uses the backup network WAN IP. So, when the primary network is down, switch the cable over. DNS servers with addresses on the primary network are unavailable, but DNS servers on the backup network are available, and vice versa. 2. Preferably, set up a dual WAN router to aggregate the bandwidth from both providers. You still need to set up the additional NS records, but in this case all are online all of the time (except during an outage for one or the other provider). A side benefit of this is that you have more bandwidth to your office for normal use. This could also help with remote access to the office in times of outage. HTH Darin. ----- Original Message ----- From: "Bill Pierson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, July 22, 2004 11:00 AM Subject: [IMail Forum] OT: Redundancy This is a little off topic, but I think this may reach my intended audience who may be able to offer some solutions. We run a small web hosting company, and have a full T1 for our main connection source. We generally have very little downtime, and our hosting clients have come to appreciate that. For the second time in 2 months, however, a major fiber line was cut and we had no phones or T1 for over 8 hours. I've gotten a cable-based "backup" connection and I'm trying to decide the best possible way to implement it as a backup for when the T1 goes down again. I only want to use the cable-based solution when the T1 goes down; no load-balancing is needed.... I have a firewall in place and use NAT/reverse proxy so that sites will come up from either (T1 or cable) Internet IP..... Has anyone had experience or could someone recommend a solution that would handle DNS ? For example, when our T1 is up and functioning, DNS points to our T1-based IP's. When the T1 goes down, DNS gets pointed to our cable-based IP's. I realize the TTL would have to be set low, but how low is too low? Again, sorry for the OT subject - any info will be sincerely appreciated. --Bill [EMAIL PROTECTED] To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
