On 06/24/2017 11:59 PM, Thomas Eckardt wrote: > > Keeps the question: Why should this query interval be changed? > The localhost's name server is almost always the fastest responder, mainly due to caching. The exception occurs when it must forward a request to one of the ISP's names servers after which the result is cached; the ISP's servers are the other two tested by ASSP. We have a very simple local network. Either the local name server has it cached, or it forwards the request to one of the ISP's servers. While the once-a-minute burden is rather light, I do not see the point of an essentially useless exercise given our system. Or I could just turn off the logging so I do not see it...
This is what the logs show 99.5% of the time. 64.119.32.100 and .101 are forwardees for the local name server: 2017-06-25 12:58:07 Info: Name Server 127.0.0.1: ResponseTime = 2 ms for sourceforge.net 2017-06-25 12:58:07 Info: Name Server 64.119.32.100: ResponseTime = 14 ms for sourceforge.net 2017-06-25 12:58:07 Info: Name Server 64.119.32.101: ResponseTime = 20 ms for sourceforge.net 2017-06-25 12:58:07 Info: Name Server 127.0.0.1: OK 2017-06-25 12:58:07 Info: Name Server 64.119.32.100: OK 2017-06-25 12:58:07 Info: Name Server 64.119.32.101: OK -- James Moe moe dot james at sohnen-moe dot com 520.743.3936 Think. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
