pgnd <[email protected]> wrote: > but, when the VM is unreachable, Bind9's fallback to direct recursion > has a very noticeable delay. in-browser reponse goes from un-noticeable > to ~ 3 seconds.
I'm curious if it's the same if the VM is up, but unbound is not running, so
you'd get an instant port unreachable, rather than suffer through ARP/ND
failures for the host.
> recommending upgrade to ?= v9.3.0, and using adaptive forwarder
> selection. but, iiuc, adaptive selection only helps when forwarders
> respond slowly -- not when completely unreachable.
I don't know the answer here, but if this VM is critical path, maybe it
should be redundant/resilient?
Why do you want this cache in place? Is it performance, anonynimity, ??
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
] My working hours and your working hours may be different. [
] Please do not feel obligated to reply outside your normal working hours [
signature.asc
Description: PGP signature
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.
