Web Hosting Forum | Lunarpages


*
Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length
February 09, 2012, 12:57:00 PM

Pages: [1]   Go Down
« previous next »
  Print  
Author Topic: Dealing with server outages  (Read 1138 times)
wektech
Master Jedi
*****
Offline Offline

Posts: 1031



WWW
« on: November 24, 2009, 02:58:02 PM »
With the recent outages documented in the forum it looks like it can take upwards of a week to get your account back to normal if a server crash happens. I find this to be rather long to have a site inoperable. This got me to wondering if I can take advantage of the fact that I have multiple accounts to deal with an outage.

As one account uses lunarbreeze dns servers and the other uses lunarservers dns I do not think their is a conflict. So could I add the sites I want to backup as add on sites on the opposite server and have them standing by in case there is a prolonged server outage. If there was a server outage, I coild then just login to tucows and repoint the domains to the server that is up.

Will this work? Would it violate the TOS?
Logged
Money savings tips for real people by real people!
Danielle
Guest
« Reply #1 on: November 24, 2009, 03:08:25 PM »
Hi wektech,

It would not violate the TOS, but DNS nameserver changes can take 24-72 hours to propagate, so were you going to repoint the new site to different nameservers by changing the nameservers? If so, then it might not work out as well for you as you'd like.

The only way to quickly change nameserver information without the high caching occurring is at the DNS zone level rather than the domain registrar level. We control the DNS zones if you are on shared servers, so it might be faster to have us change the A record for you on our end (you could still put the site up on the different location). Of course, you'd have to be clear in your email that you wanted the A record for the domain changed to the IP for the other server (and provide the IP), then provide ownership verification for both accounts in the request.

Thanks.
Logged
MNM
Galactic Royalty
*****
Offline Offline

Posts: 258


Hosted on server: TYR


WWW
« Reply #2 on: November 25, 2009, 09:49:48 AM »
Quote from: Tristan on November 24, 2009, 03:08:25 PM
It would not violate the TOS, but DNS nameserver changes can take 24-72 hours to propagate

Actually I have been shocked this year. I have changed name servers for a number of my domains and 4 hours later I was able so see them from my ISP. I went to work where I use a completely different ISP and they worked there as well.

I think this whole propagation issue is getting better. Most ISP's are updating far more frequently because its probably tying up their support lines. Now I can only speak for myself but on Sunday I changed name servers for a friend and again I was able to see the domains fairly quickly. I know it was not a cached copy because I cleared it and I changed the background color for the site on the new server.

In Canada our ISP's seem to be on the ball and updating quite frequently
Logged
MardianNaturalMedicine

MapleDomains
wektech
Master Jedi
*****
Offline Offline

Posts: 1031



WWW
« Reply #3 on: November 25, 2009, 10:16:11 AM »
I have seen DNS propagation happen within 30 minutes at least with roadrunner. When I signed up for an add on domain, the ns records pointed to the wrong name servers and I had the site up and running on the proper server very quickly. As two of my 3 domains are geared at local users, and the majority of locals use roadrunner, this would be good enough for me.

Now I just need to figure out a way to automate the database syncs between the primary and backup servers.
Logged
Money savings tips for real people by real people!
Pages: [1]   Go Up
  Print  
« previous next »
 
Jump to: