Is there a way to have a site hosted on two different servers in case one goes down? If you had the site hosted with two differnet hosts using different name servers, would that work?

For example:

ns1.host1.com
ns2.host2.com

Im am interested to know how long it would take to upload or down load a 50mg web site using Frontpage 2000 to a zip drive?

Also how do you do it?

Vic

I think you should have started a different thread for this, but it all depends on your connection speed on the internet. If you are using 56k, a long... time.

If you want to download your site using frontpage, go to "File" then choose "publish web" then click browse and choose your zip drive.

Now, back to my original question.... :)

Originally posted by deltaesoluti
Is there a way to have a site hosted on two different servers in case one goes down? If you had the site hosted with two differnet hosts using different name servers, would that work?

For example:

ns1.host1.com
ns2.host2.com

Short answer: Probably no.

Long answer: You can do that, but you need a customized DNS server that probe your web servers for downtime and send your visitors to a correct server. In short, technically you can do that, but not without spending a lot of money, at least with current technology.

You can do that, but you need a customized DNS server that probe your web servers for downtime and send your visitors to a correct server.

Well, I know if the first name sever is down the second one is suppose to takeover. Here is what I was thinking. If your DNS is on the same server as your website and that server went down, wouldn't it then use the secondary DNS and point to the backup server?

It seems like that would work unless I am missing something and I may be. :D

Originally posted by priyadi


Short answer: Probably no.

Long answer: You can do that, but you need a customized DNS server that probe your web servers for downtime and send your visitors to a correct server. In short, technically you can do that, but not without spending a lot of money, at least with current technology.

ZoneEdit does has failover capabilities, which might handle what you want to accomplish: http://www.zoneedit.com/doc/faq.html#fo

Originally posted by deltaesoluti
Is there a way to have a site hosted on two different servers in case one goes down? If you had the site hosted with two differnet hosts using different name servers, would that work?

For example:

ns1.host1.com
ns2.host2.com

ns1.host1.com
ns2.host1.com
ns3.host2.com
ns4.host2.com

I think :eek:

Of course, you'd have to FTP your site to 2 servers when you make changes. :)

Originally posted by HTTPme.com


ns1.host1.com
ns2.host1.com
ns3.host2.com
ns4.host2.com

I think :eek:

Of course, you'd have to FTP your site to 2 servers when you make changes. :)

I think that would work as long as the DNS is on the same server as the web sites.

If they are on different servers and the web site server is down, but the name sever is up, then the name server will point users to the site that is down.

If they are on the same server though, the first set of name servers would not be available and the second set of nameservers should take over and point to the site on the second server which would be up.

Does that make any sense? :confused:

Originally posted by deltaesoluti


I think that would work as long as the DNS is on the same server as the web sites.

If they are on different servers and the web site server is down, but the name sever is up, then the name server will point users to the site that is down.

If they are on the same server though, the first set of name servers would not be available and the second set of nameservers should take over and point to the site on the second server which would be up.

Does that make any sense? :confused:

You've just given me a headache :eek: :confused: :D

Originally posted by HTTPme.com


You've just given me a headache :eek: :confused: :D

You have one too? :D

Originally posted by deltaesoluti


Well, I know if the first name sever is down the second one is suppose to takeover. Here is what I was thinking. If your DNS is on the same server as your website and that server went down, wouldn't it then use the secondary DNS and point to the backup server?

It seems like that would work unless I am missing something and I may be. :D


Yes, but when both server are up, your visitors will use both server randomly, not exactly a 'failover', more like a 'load balancing' to me :). I'm not sure if it is fine with you.

Originally posted by Dave114


ZoneEdit does has failover capabilities, which might handle what you want to accomplish: http://www.zoneedit.com/doc/faq.html#fo

Great... thanks for the info.

Originally posted by priyadi



Yes, but when both server are up, your visitors will use both server randomly, not exactly a 'failover', more like a 'load balancing' to me :). I'm not sure if it is fine with you.

I thought the secondary DNS was only used if the primary failed. Is that not correct? :confused:

There have been a lot of discussions about this on here.

http://www.webhostingtalk.com/showthread.php?s=&threadid=28780

Originally posted by bitserve
There have been a lot of discussions about this on here.

http://www.webhostingtalk.com/showthread.php?s=&threadid=28780

Thanks that was very helpful. I think the email issue would be difficult to resolve. I had not thought about that. I think this suggestion would solve the email issue.

"As to the mail issue, the simplest resolution is to set weighted mail records in both zone files. Make your primary host have the lower weight, and the secondary host have the higher weight. If your primary host goes down, the secondary host will queue the mail and try to deliver it to your primary host for up to 5 days (If your host is down longer than 5 days you have much more serious problems ). This will always keep mail directed to your primary server, and you shouldn't lose any mail during an outage. You won't be able to check it, but you won't lose it."

Ok, I think I have this figured out. :cool:

I could have the same .com site on two different severs.

Each server would have its own set of name servers.

If the first server went down the second one would take over.

On the second server I could have the email for that .com set to forward to a third party pop email account. That way the email would not get stuck on the second server when the first server came back up.

The third party pop email could be set up to pull into the user's Outlook or other email program.

How about that?? :cool:

search "round robin"

Originally posted by deltaesoluti
Ok, I think I have this figured out. :cool:

I could have the same .com site on two different severs.

Each server would have its own set of name servers.

If the first server went down the second one would take over.

On the second server I could have the email for that .com set to forward to a third party pop email account. That way the email would not get stuck on the second server when the first server came back up.

The third party pop email could be set up to pull into the user's Outlook or other email program.

How about that?? :cool:


I think that's won't be necessary. If configured properly, your second server will deliver your mails to the first server once it came back up.

Originally posted by priyadi



I think that's won't be necessary. If configured properly, your second server will deliver your mails to the first server once it came back up.

how?

How? For DNS, you need to set up MX records as other poster has pointed out. For mail server, consult your mail server configuration. Basically you need both server configured to receive mail from your domain, but only your first server delivers emails locally, the second one should try to forward them to the first server.

Originally posted by priyadi
How? For DNS, you need to set up MX records as other poster has pointed out. For mail server, consult your mail server configuration. Basically you need both server configured to receive mail from your domain, but only your first server delivers emails locally, the second one should try to forward them to the first server.

If I set the second server to forward mail to the first server, then email would not be accessible while the first server is down.

If I forward email to a third party from the second server, then the users would be able to access their emails the entire time. They would not have to wait till the first server came back up.