On Tuesday, June 23, 2015 08:35:50 AM Thomas Eckardt wrote: > 'DNSResponseLog' - will show you why the DNS-server order is switched > > 'maxDNSRespDist' - set this value high to prevent DNS-server switching > > >The order should be fixed IMHO. > > The rule is: "use the fastest answering DNS-server first"
Actually not the case, in my case there was some problems with reverse delegation lookup on localhost. That cause ASSP to think there was DNS issues and swap around DNS servers. When the actual DNS resolution response time was always good. Also it tried using DNS servers that were having issues, thus having them last in the list. Thus it is NOT making good decisions as to which DNS servers to use. While one might seem faster at a given moment. That does not mean its more reliable. But then again the main issue was a failure with localhost PTR lookup, not with actual DNS lookups. Not exactly sure why ASSP is doing a reverse lookup on localhost and why that matters. None the less I fixed that aspect of my DNS servers and ASSP is happy now. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
