Hello,
I’m seeking guidance on configuring DNS Traffic Control (DTC) to implement load balancing based on priority in my current setup.
Here’s the scenario: I have two datacenters (DCs)—one is primary and the other is secondary. All applications hosted in the primary DC are backed up in the secondary DC. I want to configure DTC so that traffic destined for a given application is always directed to the server in the primary DC, as long as it’s up and running (health monitors will be used to check service availability). If the primary server becomes unavailable, the DNS should then direct traffic to the backup server in the secondary DC.
In my configuration attempt, I created both primary and secondary servers for each application, added them to pools, and configured health monitors. However, I ran into an issue: I couldn’t find a load balancing method that prioritizes one server over another. The available methods—such as “All Available,” “Ratio: Dynamic,” “Global Availability,” “Round Robin,” and others—don’t seem applicable to my needs.
I did notice that DTC supports setting a priority for LBDNs (which could potentially help prioritize one LBDN over another when LBDNs patterns overlap). However, this approach seems to require creating twice the number of LBDNs, which may not be practical.
Does DTC natively support priority-based load balancing for domain names? If not, are there any alternative methods I can use to achieve the desired behavior?
Any insights or suggestions would be greatly appreciated. Thanks in advance for your help!
204 
0
