26 Dub
2025
26 Dub
'25
19:34
On Sat, Apr 26, 2025 at 12:20 PM Jeremy C. Reed <reed(a)reedmedia.net> wrote:
I didn't try it, but since this says "remote" maybe define multiple
remotes with one remote for each address.
There are a few places where I have found the behaviour to be best if I
treat each remote ID as an individual server. One other example in the
handling of zone transfers is when an upstream IP address is unreachable...
a different remote per server allows Knot to try a different remote, where
clustering them all together causes the entire *XFR to fail. So in our
configs, an individual remote gets at most one each of an IPv4 and IPv6
address, and I might even consider splitting _those_ up (as you suggest
above) if you want to handle the case where a server is reachable in one
protocol but not the other.