<div dir="ltr"><div dir="ltr"><div><div>Kevin,<br></div>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 is like it is not caching any external results so maybe it needs to go out and do all lookups again to make sure signature valid? I really don't know. I'm now guessing.<br><br></div>I will try your suggestion of logging again, and as for link local, yes, couple of years ago we saw problems<br><br></div><div>ed<br></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 11, 2019 at 1:17 AM Kevin Darcy <<a href="mailto:kevin.darcy@fcagroup.com">kevin.darcy@fcagroup.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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. (Although, on the other hand, you mentioned VoIP, and VoIP sometimes requires applying QoS at the LAN level too).<div><br></div><div>You currently have query logging turned off. If it's not too resource-intensive, you might want to consider turning that on, to verify whether the queries are getting to BIND. Or, run a packet capture on the BIND side. Packet capture on the BIND device should also help to identify any issues talking upstream (e.g. to TLD servers or auth servers for domains like <a href="http://google.com" target="_blank">google.com</a>). Packet capture on the *client* side would probably be necessary for definitive proof of whether replies are being dropped by the LAN (compare what the server sent side-by-side with what the client saw).</div><div><br></div><div>I was intrigued by "server fe80::/16 { bogus yes; }; " in your config. Have you had issues with IPv6 link-local addresses being associated with delegated nameservers? I haven't noticed this, but then again, I haven't been looking for that particular misconfiguration specifically...</div><div><br></div><div> - Kevin<br><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 10, 2019 at 12:06 AM Edwardo Garcia <<a href="mailto:wdgarc88@gmail.com" target="_blank">wdgarc88@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div><div>With new windows update last day, we notice something strange, our local DNS cache server timeout on lookups.<br><br></div>For example lookup <a href="http://google.com" target="_blank">google.com</a>, 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 doesnt cacher it for even 1ns it seems<br><br></div>QoS on router gives DNS (udp and tcp)and VoIP highest priority, everything else is default QoS must be working because if I do <br>host <a href="http://www.google.com" target="_blank">www.google.com</a> $externalDNSserver I get an answer pretty much right away, immediately try again on our local dns server it times out cant connect to any servers.<br></div><div>this contrinues on, if I drop the LAN port on switch the windows update machine uses, it resolves <a href="http://google.com" target="_blank">google.com</a> again, bring back up that port, it times out again.<br><br></div><div>this only happens on congestion, with our cable link maxed out.<br><br></div><div>(never thought i'd see the day when a windows pc would take out an entire network)<br><br></div><div>Below is my named.conf I have to be missing something ?<br> <br>BIND 9.11.2-P1<br>running on Linux i686 3.16.58 #1 SMP Sat Sep 29 11:06:24 AEST 2018<br>built by make with defaults<br><br>acl "trusted" { localhost; <a href="http://198.162.100.0/24" target="_blank">198.162.100.0/24</a>; };<br>acl "sysop" { localhost; 192.168.100.6; };<br> <br>options {<br> directory "/var/named";<br> allow-query { trusted; }; <br> allow-query-cache { trusted; };<br> allow-transfer { sysop; };<br> transfer-format many-answers;<br> masterfile-format text;<br> interface-interval 0;<br> response-policy {zone "rpz.lan"; };<br> dnssec-enable yes;<br> dnssec-validation auto;<br> empty-zones-enable yes;<br>};<br><br>server fe80::/16 { bogus yes; };<br> <br>logging {<br> category lame-servers { null; };<br> category edns-disabled { null; };<br> category client { null; };<br> category dnssec { null; };<br> //channel log_queries { file "/var/named/query.log"; print-category yes; };<br> //category queries { log_queries; };<br> channel log-rpz { file "/var/log/rpz.log" versions 10 25m; severity info; };<br> category rpz { log-rpz; };<br>};<br> <br>zone "." {<br> type hint;<br> file "root.cache";<br> <br>zone "rpz.lan" {<br> type master;<br> file "rpz.lan";<br> allow-query { trusted; };<br> allow-update {none;};<br> notify no;<br>};<br> <br> <br>zone "<a href="http://akamai.net" target="_blank">akamai.net</a>" {<br> type forward;<br> forward first;<br> forwarders { xxxxxx; xxxxxx; };<br>};<br> <br> <br><br></div></div></div></div></div></div></div>
_______________________________________________<br>
Please visit <a href="https://lists.isc.org/mailman/listinfo/bind-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list<br>
<br>
bind-users mailing list<br>
<a href="mailto:bind-users@lists.isc.org" target="_blank">bind-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/bind-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/bind-users</a><br>
</blockquote></div>
</blockquote></div></div>