OK, so this happen again, with link congestion.
bind is caching the results as tested with no congestion, 78ms down to
1ms... BUT the issue with bind remain and logs show nothing wrong
congested link lookup , tried in instant succession with a second or less
between:
google.com (like any other h
Kevin,
I though lan saturation too, but I can ssh into bind server immediately, I
also, from my other pc did a lookup on local authoritative zone rpz.lan, so
my bind replying right away or within 1 second during congestion, could it
be dnssec the problem, I did not disable that to test, it really i
Offhand, sounds like your LAN is saturated so the queries might not be
getting to BIND in the first place. Or the replies aren't getting back.
It's unlikely that QoS is going to help this, you indicated that QoS was on
your "router", and that is typical -- usually QoS is found on WAN links.
(Althou
With new windows update last day, we notice something strange, our local
DNS cache server timeout on lookups.
For example lookup google.com, 1 minute later fails timeout looking up, but
since it has already looked it up it should have returned answer from cache
yes? google has a 5min TTL, my cache
4 matches
Mail list logo
