NSS — Sat, 24 Mar 2001 18:15:29 +0000

I agree it's quite a hassle and it the only way at the moment. If I come across something new or how to update files for both Hosts automatically or simultaneously I will post here.

mjames — Sat, 24 Mar 2001 17:58:40 +0000

Quote: Originally posted by NSS
1) You can create any amount of FTP account, just select new and that's it. For every new account, you must enter the IP(or your site e,g. abc.com if it's already propogated), username, & password that your Host provide you to upload files to their server.

No, no. I understand how to do this, but in my opinion, it would be a hassle to have to keep both FTP accounts identical and current. For example, if I make a change to a certain HTML page, I have to connect on one account, upload, disconnect, connect on the other, upload, and then disconnect. But, I do see your point with this. Just not something I'd be interested in doing.

NSS — Sat, 24 Mar 2001 00:24:24 +0000

1) You can create any amount of FTP account, just select new and that's it. For every new account, you must enter the IP(or your site e,g. abc.com if it's already propogated), username, & password that your Host provide you to upload files to their server.

2) Yes, It's a bit more expensive.

mjames — Fri, 23 Mar 2001 21:35:34 +0000

Two problems first come to my mind:

1. How do you manage uploading identical versions of files on both servers? For me, it would be quite a hassle with switching FTP sessions and upload again.

2. Two hosts costs double the price.

NSS — Fri, 23 Mar 2001 12:53:42 +0000

I agree with John,

Quote: Moreover, this technique applies to websites with limited content and not dynamic driven web pages.

It's not fully tested. Hehe, please use this method at your own risk.

Fri, 23 Mar 2001 10:13:08 +0000

That's a very good tip about creating mirror websites that act as backup. However is some cases, the domain name server can be up and running and in the same time the website can be down. Some web hosting companies are using external domain name servers which are usually 100% up. In that case your domain can be resolved but without displaying the website.

Moreover, this technique applies to websites with limited content and not dynamic driven web pages. The suggested solution for these websites is two or more ips are pointing to the same machine ( same web hosting company ) but by using different connections. That could prevent you from downtime when a line is down for some reason. On the other hand I don't know many web hosting companies that allow this.

Best Regards,

NSS — Wed, 21 Mar 2001 15:56:27 +0000

You can mark your index page for one server so that you will be able to know each time you access your site, which server is being used.

It acts more like a backup in case one server cannot be connect then it automatically looks for the other nameservers and this way you can be assure of getting a connection from the other server.

If I am not mistaken recently about a month back some routing failure occurred in Taiwan and followed by the VDI failure most sites were down for days and when it was rectified all those affect took another few days to propogate throughout the Internet before everything was back to normal.

Fearing for future occurrence, me and my friends thought of this idea.

Ravi Pachai — Wed, 21 Mar 2001 14:49:54 +0000

I've never thought of that but it sounds like a great idea! How often do you find the second host gets used?

Ravi

Jaiem — Wed, 21 Mar 2001 14:03:50 +0000

So how does the net know which name server to use for lookups?