Very suspicious of listen-address=127.0.0.9. Are you sure you've not
created a loop where dnsmasq is send queries back to itself?
Enabling logging, and/or --dns-loop-detect would be useful.
Cheers, Simon.
On 5/1/24 23:47, Kenneth Berland wrote:
On March 2, 2020 (possibly causing the Pandemic?), there was a thread
with this name that went unresolved. I'm facing the same issue with
dnsmasq-2.90 and the following configuration. After about 10 minutes,
dnsmasq starts to consume 100% of the CPU. I'm running like this:
$ wget https://thekelleys.org.uk/dnsmasq/dnsmasq-2.90.tar.xz
<https://thekelleys.org.uk/dnsmasq/dnsmasq-2.90.tar.xz>
$ tar -xf dnsmasq-2.90.tar.xz
$ cd dnsmasq-2.90
$ make
$ sudo ./src/dnsmasq -k
$ cat /etc/dnsmasq.conf | grep -v ^# | awk NF
address=/run.app/199.36.153.11 <http://run.app/199.36.153.11>
bind-interfaces
listen-address=127.0.0.9
-KB
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
