The existing --elb-dnsname flag works to setup route53 aliases that point to elastic load balancers.
Ex.
$ denominator -n route53 record -z Z3I0BTR7N27QRM replace -t A -n abadmin.us-east-1.dynprod.netflix.net. --elb-dnsname abadmin-795710131.us-east-1.elb.amazonaws.com.
In a failure case, you can use the record replace command to re-point these to healthy loadbalancers. However, this requires you to lookup the specific ELB name, which can be error prone.
Note you need to know the healthy ELB hostname somehow!
$ denominator -n route53 record -z Z3I0BTR7N27QRM replace -t A -n abadmin.us-east-1.dynprod.netflix.net. --elb-dnsname abadmin-126115512.us-west-2.elb.amazonaws.com.
This change adds two flags which allow you to point route53 aliases to other aliases. This means you don't have to look up ELB instances anymore during failover.
Ex.
$ denominator -n route53 record -z Z3I0BTR7N27QRM replace -t A -n abadmin.us-east-1.dynprod.netflix.net. --alias-hosted-zone-id=Z3I0BTR7N27QRM --alias-dnsname abadmin.us-west-2.dynprod.netflix.net.
The existing
--elb-dnsname
flag works to setup route53 aliases that point to elastic load balancers.Ex.
In a failure case, you can use the
record replace
command to re-point these to healthy loadbalancers. However, this requires you to lookup the specific ELB name, which can be error prone.Note you need to know the healthy ELB hostname somehow!
This change adds two flags which allow you to point route53 aliases to other aliases. This means you don't have to look up ELB instances anymore during failover.
Ex.