Microsoft Azure Traffic Azure Failover from On-Premises Website to Azure Website
Hello,
We would like to use Microsoft Azure's Traffic Manager to failover from a corporate public facing on-premises website to a website that is hosted in Microsoft Azure. I'm having problems getting Microsoft Azure Traffic Manager to failover correctly to my test on-premises website.
So far I've done the following:
1. Created a test on-premises website (test.company.com).
2. Created a CNAME Record test1.company.com which points to test.trafficmanager.net (the Azure Traffic Manager Profile).
3. test.company.com and test1.company.com use the same A Record.
4. Created a test Azure Website test.cloudapp.net
5. Created a test Azure Traffic Manager Profile with two external endpoints test1.company.com and test.company.com and one Azure endpoint for test.cloudapp.net. I created this profile with Azure Powershell and added the external endpoints through Azure Powershell. When I view my test.trafficmanager.net profile in Azure I can see that they are added correctly.
When I stop test.company.com to simulate a failover I would expect that it should failover to test.cloudapp.net. The failover works for test1.company.com but does not work for test.company.com. I get a 404 Not Found error for test.company.com.
Does anyone have experience with how to configure the DNS correctly to get failover to work with Azure Traffic Manager?
Thank you.
We would like to use Microsoft Azure's Traffic Manager to failover from a corporate public facing on-premises website to a website that is hosted in Microsoft Azure. I'm having problems getting Microsoft Azure Traffic Manager to failover correctly to my test on-premises website.
So far I've done the following:
1. Created a test on-premises website (test.company.com).
2. Created a CNAME Record test1.company.com which points to test.trafficmanager.net (the Azure Traffic Manager Profile).
3. test.company.com and test1.company.com use the same A Record.
4. Created a test Azure Website test.cloudapp.net
5. Created a test Azure Traffic Manager Profile with two external endpoints test1.company.com and test.company.com and one Azure endpoint for test.cloudapp.net. I created this profile with Azure Powershell and added the external endpoints through Azure Powershell. When I view my test.trafficmanager.net profile in Azure I can see that they are added correctly.
When I stop test.company.com to simulate a failover I would expect that it should failover to test.cloudapp.net. The failover works for test1.company.com but does not work for test.company.com. I get a 404 Not Found error for test.company.com.
Does anyone have experience with how to configure the DNS correctly to get failover to work with Azure Traffic Manager?
Thank you.
ASKER
Thanks for your comments shalmoc. I think IIS is configured correctly because the test.company.com website works correctly when the site is running. To simulate the failover I stopped the site on our hardware load balancer. That's when I'm not able to access test.company.com. At this point it should failover to the test.cloudapp.net.
Could you please let me know what you think should change with the IIS configuration.
Thanks.
Could you please let me know what you think should change with the IIS configuration.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The solution provided was not correct. IIS was configured correctly. We were able to get the problem resolved ourselves.
That is because 404 is file not found error, and it is the response returned by a web server. So the DNS resolves to a web server that does not recognize the "test.company.com" virtual host.
In other words, your DNS is good, your IIS is not.