Multiple targets for a single DNS record
Hi, we are using non-hosted zones with multiple records to load balance between VMs.
It seems a bit wrong to have multiple identical records, one can have TLS enabled and one can have it disabled, but this is incorrect, as both will likely have TLS, as the LB seems to enable TLS even if only one is enabled.
A suggestion that would be more logical for this, would be to have a single record, and then allow multiple targets instead. This way we only add a single @ record, enable TLS, and point it to app-1 and app-2, etc.
- Jake Warner...
Hi Niels,
We actually introduced this functionality about a month ago, but only for HTTP routing.
In your DNS record, if you click Advanced at the bottom, you’ll see an option called Traffic Splitting. You can add variants there. :)
Keep in mind the default route always has a weight of 100 and cannot be disabled. But if you added another route, and gave it a weight of 100, it would receive 50% of the traffic. (Two routes of equal 100 weight)
Does this solve what you’re looking to do?
Join the conversation
Sign in with your Cycle account to reply to this thread.