Expected Behaviour:
No logfile spam.
Actual Behaviour:
My pihole.log is spammed with weird requests endlessly. It repeats the query loop every second. This started a while ago, I have no idea what the cause might be.
Only difference is that I have now enabled DNSv6 as well.
Jan 22 23:45:50 dnsmasq[15746]: config cachesize.bind is <TXT>
Jan 22 23:45:50 dnsmasq[15746]: config insertions.bind is <TXT>
Jan 22 23:45:50 dnsmasq[15746]: config evictions.bind is <TXT>
Jan 22 23:45:50 dnsmasq[15746]: config hits.bind is <TXT>
Jan 22 23:45:50 dnsmasq[15746]: config misses.bind is <TXT>
Jan 22 23:45:50 dnsmasq[15746]: config auth.bind is <TXT>
Jan 22 23:45:50 dnsmasq[15746]: config servers.bind is <TXT>
Jan 22 23:45:51 dnsmasq[15746]: config cachesize.bind is <TXT>
Jan 22 23:45:51 dnsmasq[15746]: config insertions.bind is <TXT>
Jan 22 23:45:51 dnsmasq[15746]: config evictions.bind is <TXT>
Jan 22 23:45:51 dnsmasq[15746]: config hits.bind is <TXT>
Jan 22 23:45:51 dnsmasq[15746]: config misses.bind is <TXT>
Jan 22 23:45:51 dnsmasq[15746]: config auth.bind is <TXT>
Jan 22 23:45:51 dnsmasq[15746]: config servers.bind is <TXT>
Jan 22 23:45:52 dnsmasq[15746]: config cachesize.bind is <TXT>
Jan 22 23:45:52 dnsmasq[15746]: config insertions.bind is <TXT>
Jan 22 23:45:52 dnsmasq[15746]: config evictions.bind is <TXT>
Jan 22 23:45:52 dnsmasq[15746]: config hits.bind is <TXT>
Jan 22 23:45:52 dnsmasq[15746]: config misses.bind is <TXT>
Jan 22 23:45:52 dnsmasq[15746]: config auth.bind is <TXT>
Jan 22 23:45:52 dnsmasq[15746]: config servers.bind is <TXT>
Jan 22 23:45:53 dnsmasq[15746]: config cachesize.bind is <TXT>
Jan 22 23:45:53 dnsmasq[15746]: config insertions.bind is <TXT>
Jan 22 23:45:53 dnsmasq[15746]: config evictions.bind is <TXT>
Jan 22 23:45:53 dnsmasq[15746]: config hits.bind is <TXT>
Jan 22 23:45:53 dnsmasq[15746]: config misses.bind is <TXT>
Jan 22 23:45:53 dnsmasq[15746]: config auth.bind is <TXT>
Jan 22 23:45:53 dnsmasq[15746]: config servers.bind is <TXT>
Jan 22 23:45:54 dnsmasq[15746]: config cachesize.bind is <TXT>
Jan 22 23:45:54 dnsmasq[15746]: config insertions.bind is <TXT>
Jan 22 23:45:54 dnsmasq[15746]: config evictions.bind is <TXT>
Jan 22 23:45:54 dnsmasq[15746]: config hits.bind is <TXT>
Jan 22 23:45:54 dnsmasq[15746]: config misses.bind is <TXT>
Jan 22 23:45:54 dnsmasq[15746]: config auth.bind is <TXT>
Jan 22 23:45:54 dnsmasq[15746]: config servers.bind is <TXT>
Jan 22 23:45:55 dnsmasq[15746]: config cachesize.bind is <TXT>
Jan 22 23:45:55 dnsmasq[15746]: config insertions.bind is <TXT>
Jan 22 23:45:55 dnsmasq[15746]: config evictions.bind is <TXT>
Jan 22 23:45:55 dnsmasq[15746]: config hits.bind is <TXT>
Jan 22 23:45:55 dnsmasq[15746]: config misses.bind is <TXT>
Jan 22 23:45:55 dnsmasq[15746]: config auth.bind is <TXT>
The log grows rapidly. This is the number of entries generated by those answers from within the last 6 hours.
/var/log $ cat pihole.log | grep -i bind |wc -l
75637
Is there any explanation what is generating those requests and who is endlessly querying my "config"? How can I pin down which client is causing them, since there is no client info / request origin given.
Hot to fix this?
Further I noticed in Diagnosis:
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Expires: Fri, 22 Jan 2021 22:47:15 GMT
Cache-Control: max-age=0
Date: Fri, 22 Jan 2021 22:47:15 GMT
Server: lighttpd/1.4.53
Does this affect Pi-Hole functionality in any way?
