Package: dnsmasq Version: 2.68-1 Severity: normal Dear Maintainer,
When dnsmasq is being overwhelmed with queries, it tends to flood syslog with messages like this: ,---- | Jan 21 03:15:31 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:04 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:10 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:16 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:22 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:28 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:34 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:40 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:46 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:52 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:17:58 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:04 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:10 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:16 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:22 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:28 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:34 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:40 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:46 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:52 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:18:58 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:04 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:10 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:16 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:22 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:28 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:34 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:40 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:46 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:52 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:19:58 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:20:04 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:20:10 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:20:16 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:20:22 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:20:28 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) | Jan 21 03:20:34 hydrogen dnsmasq[4637]: Maximum number of concurrent DNS queries reached (max: 500) `---- It would be nice if it could try to emit these warnings a bit less frequently, perhaps using some other means to indicate the severity of the problem if it continues to occur. (These particular warnings were with "dns-forward-max=500"; I had been hoping that setting would get rid of most of the warnings but it really didn't seem to do much better than the default of 150.) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.9-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dnsmasq depends on: ii dnsmasq-base 2.68-1 ii netbase 5.2 dnsmasq recommends no packages. Versions of packages dnsmasq suggests: ii resolvconf 1.74 -- Configuration Files: /etc/dnsmasq.conf changed: server=2001:4de0:1000:a4::2 server=2001:4de0:1000:a3::2 all-servers no-dhcp-interface=br0 cache-size=1500 bogus-nxdomain=63.251.179.51 bogus-nxdomain=8.15.7.100 conf-dir=/etc/dnsmasq.d -- no debconf information -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
