On 3/31/21 10:00 AM, Tony Finch wrote:
Because of this, if it's important for you to avoid multi-second
DNS lookup times ... you need to design your system so that the libc
resolver never tries to talk to a DNS server that isn't available.
I've seen various client OSs fail in really weird
Tom Preissler wrote:
>
> at my work place we have a three resolver setup in /etc/resolv.conf.
>
> We had sometimes, though rarely, response times for DNS like 14000ms,
> due to the fact that the *first* listed resolver is down for maintenance
> reasons.
Sadly the traditional unix stub resolver
On 31.03.21 10:56, Tom Preissler via bind-users wrote:
at my work place we have a three resolver setup in /etc/resolv.conf.
resolv.conf is not a BIND thing, it's configuration of system libraries.
We had sometimes, though rarely, response times for DNS like 14000ms,
due to the fact that the
Hi,
at my work place we have a three resolver setup in /etc/resolv.conf.
We had sometimes, though rarely, response times for DNS like 14000ms,
due to the fact that the *first* listed resolver is down for maintenance
reasons. The application we test this with is Oracle/TNSPing.
As a mitigation we
4 matches
Mail list logo