There was a outage in July 2009 of Authorize.Net's websites because of a local fire. If you went to their website during that time there was a notice or redirection to view status updates on their Twitter account. That seemed like a good solution.
That got me thinking. For the websites I manage, in their current setup, if my host lost total internet connection the user would see a 'Server not found' error in their browser. I'd hate to have visitors think the company was no longer in business. I'd favor having the visitor see some kind of 'Unplanned outage' page.
Currently I'd have to:
- Notice the site was down (ip monitoring)
- Update the Nameserver's DNS records to point to another host (hopefully already setup)
- Wait for the new DNS records to propagate (25 mins - 48hrs)
This seems like a horrible solution. I know there has to be a better way of doing this.
Question #1: What is a solution to avoid this?
An idea I had would be to have Nameserver 1 & 2 pointed to nameservers physically located where the website is hosted. And to have Nameserver 3 & 4 pointed to another host where a 'Unplanned outage' page can be viewed.
Question #2: Would this solution work?
Question #3: Can I rely on the nameservers being queried in order (1,2,3,4)?
Question #4: Is this a horrible idea or frowned upon?