DXD
2007-10-10, 13:22 PM
Can anyone tell me what the best way to handel something like the following.
We have a production web server at our office and our dns is handled by our ISP, we are adding a Disaster Recovery site in another state and will be log shipping sql and stuff to it to keep it up todate.
My question though is in an event of failure here at our office, what is the best way to redirect traffice to our domain name to the dr site. I know we could have our ISP change the dns to the other ipaddress but is there something that would be quicker? Something that can happen in 1hr or less.
I thought maybe having 2 a records with the same name and different ips and having the dr site just redirect all traffic to our office ip unless we are down then we could manually take that redirect out, but I was not sure if hostheaders are passed on a ASP response.redirect or not and was not sure if we redirected to an IP if the domain would stay in the browser.
We have a production web server at our office and our dns is handled by our ISP, we are adding a Disaster Recovery site in another state and will be log shipping sql and stuff to it to keep it up todate.
My question though is in an event of failure here at our office, what is the best way to redirect traffice to our domain name to the dr site. I know we could have our ISP change the dns to the other ipaddress but is there something that would be quicker? Something that can happen in 1hr or less.
I thought maybe having 2 a records with the same name and different ips and having the dr site just redirect all traffic to our office ip unless we are down then we could manually take that redirect out, but I was not sure if hostheaders are passed on a ASP response.redirect or not and was not sure if we redirected to an IP if the domain would stay in the browser.