Using Traffic Manager for DR

Category: azure virtualnetwork


chabrown2018 on Thu, 09 Nov 2017 15:49:16

Newbie testing Traffic Manager

We are setting up ASR to fail On-Prem over to Azure during DR scenario. We would like to use traffic manager Priority to speed up the time for Public websites to be online. We are able to setup traffic profile for a traditional website and it works. I also have a netscaler that we set up a public endpoint on Azure and point traffic manager to use public ip. The issue is once i use the traffic manager url for Azure the netscaler has a redirect and sends the traffic https://netscalertest/vpn/index.html so I'm back using our On-Prem environment. Is there a way that I can tell traffic manager to use an url instead of public ip? I'm thinking if i able to send traffic to https://netscalertest/vpn/index.html instead then i won't be redirected.


Nirushi J on Fri, 10 Nov 2017 07:46:41

Can you tell us a bit more about the endpoints you have behind the Traffic Manager.

Are you setting them up as external endpoints? Since Traffic Manager currently supports only DNS names for endpoints (vs IPv4 / IPv6 addresses), for the endpoint in Azure are you using the DNS name associated with the public IP address?

When you try to connect directly to that public IP, does it show the same redirect behavior?


Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members

Jonathan Tuliani on Fri, 10 Nov 2017 10:54:18

I'm not clear on exactly what you're trying to do, or what the issue is that you're experiencing. However, reading between the lines, I suspect you have a misunderstanding about how Traffic Manager works. Please note that Traffic Manager is a DNS-based system.  It directs traffic to the correct endpoint using DNS, and clients then connect to those endpoints directly. It is not a proxy and traffic does not flow through Traffic Manager. This article should help: