Details to "WARNING: Detected slow or failing DNS service response XX time(s)."
Posted in 2023
Topics: General Discussion
Hi! Does anyone have more detailed information on " WARNING: Detected slow or failing DNS service response XX time(s)." What is the threshhold for "slow"? Can I activate any logging, to get the slow DNS-Response (Windows)? What I currently now (or think to now) from the online-log: 07/10/2023 21:56:35 WARNING: Detected slow or failing DNS service response 1101 time(s). 07/11/2023 09:30:07 WARNING: Detected slow or failing DNS service response 1201 time(s). 07/11/2023 19:06:11 WARNING: Detected slow or failing DNS service response 1301 time(s). 07/12/2023 08:20:18 WARNING: Detected slow or failing DNS service response 1401 time(s). 07/12/2023 13:15:47 WARNING: Detected slow or failing DNS service response 1501 time(s). 07/13/2023 05:51:08 WARNING: Detected slow or failing DNS service response 1601 time(s). 07/14/2023 07:20:40 WARNING: Detected slow or failing DNS service response 1701 time(s). 07/17/2023 01:21:22 WARNING: Detected slow or failing DNS service response 1801 time(s). 07/18/2023 21:21:35 WARNING: Detected slow or failing DNS service response 1 time(s). 07/19/2023 07:30:06 WARNING: Detected slow or failing DNS service response 26 time(s). 07/19/2023 14:22:29 WARNING: Detected slow or failing DNS service response 51 time(s). 07/20/2023 04:49:21 WARNING: Detected slow or failing DNS service response 76 time(s). 07/20/2023 11:11:43 WARNING: Detected slow or failing DNS service response 101 time(s). 07/21/2023 10:47:44 WARNING: Detected slow or failing DNS service response 201 time(s). 07/24/2023 07:19:33 WARNING: Detected slow or failing DNS service response 301 time(s). "time(s)" is since last Service-Start (not since last log-message) Every 100times (>100) will produce an logentry Thx ------------------------------ Kind Regards Stefan ------------------------------
S. onstat -g cfg full REPORT_SLOW_DNS_THRESHOLD + onstat -g cfg full REPORT_SLOW_DNS_FREQUENCY
The REPORT_SLOW_DNS_THRESHOLD parameter is the maximum duration of a
DNS call (such as gethostbyname()) in miliseconds. If a DNS call exceeds
this duration the server will write a warning message to the log and
increment the slow_dns profile element. Also see REPORT_SLOW_DNS_FREQUENCY.
The REPORT_SLOW_DNS_FREQUENCY parameter governs how often a warning
message will be written to the log when the slow_dns profile element is
incremented. Also see REPORT_SLOW_DNS_THRESHOLD.
Unfortunately there's no information on what exact DNS lookup is taking so long, but good candidates always are DNS reverse lookups on client host's IP addresses.
HTH,
Andreas
------------------------------
Andreas Legner
------------------------------
slow_DNS is reported when looking at the hostname takes more time than the allotted time in milliseconds to get the info.
By default REPORT_SLOW_DNS_THRESHOLD=200
You can change this value by updating the entry in onconfig. Everytime a hostname lookup takes more than 200 milliseconds it adds 1 to the slow_DNS counter.
https://www.oninit.com/onstat/pda.php?id=onstat%20-g%20ntt