There’s also a feature to let ATS use an expired DNS record while updating it.
It’s very useful, I use it all the time.
— Leif
> On Oct 18, 2018, at 13:46, Alan Carroll
> wrote:
>
> Unfortunately multiple addresses per host in a host file used to work but
> was broken in the last HostDB upda
Thanks Alan, that’d be awesome if we can bring it back.
> On Oct 18, 2018, at 12:46 PM, Alan Carroll
> wrote:
>
> Unfortunately multiple addresses per host in a host file used to work but
> was broken in the last HostDB update. I don't think it would be that hard
> to put back.
>
> On Thu, O
Thanks Aaron! That’s what I needed.
Bhasker.
> On Oct 18, 2018, at 12:13 PM, Aaron Canary wrote:
>
> The code parsing and storing the host_file only keeps 1 IpAddr per
> hostname.
> In order to use proxy.config.hostdb.strict_round_robin, the record must
> come through DNS.
>
> *I am trying t
Unfortunately multiple addresses per host in a host file used to work but
was broken in the last HostDB update. I don't think it would be that hard
to put back.
On Thu, Oct 18, 2018 at 2:13 PM Aaron Canary
wrote:
> The code parsing and storing the host_file only keeps 1 IpAddr per
> hostname.
>
The code parsing and storing the host_file only keeps 1 IpAddr per
hostname.
In order to use proxy.config.hostdb.strict_round_robin, the record must
come through DNS.
*I am trying to get the same thing working with hostdb since I want to
> avoid DNS round trip because my IPs are fairly fixed.*
Yo
Hi,
I am looking at the hostdb configuration and I need some clarification on
the configuration. In particular I have questions about these two
configuration parameters.
proxy.config.hostdb.host_file.path
proxy.config.hostdb.strict_round_robin
I am trying to understand how hostdb round_robin conf
