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.
COV-WebmasterCity Of VancouverAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shalom CarmelCTOCommented:
404 means that something is misconfigured on test.company.com failover server.
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.
0
COV-WebmasterCity Of VancouverAuthor Commented:
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.
0
COV-WebmasterCity Of VancouverAuthor Commented:
We recreated our DNS entries with the CNAME pointing to the Azure Traffic Manager and it is working now.  There may have been an issue with the DNS changes propagating correctly the first time.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
COV-WebmasterCity Of VancouverAuthor Commented:
The solution provided was not correct.  IIS was configured correctly.  We were able to get the problem resolved ourselves.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Azure

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.