jfb
January 11, 2022, 2:29am
2
The warnings have always existed in /var/log/pihole.log . A change to Pi-hole made them more visible by also printing them into /var/log/pihole-FTL.log and showing them on the dashboard.
https://github.com/pi-hole/FTL/pull/1243
https://pi-hole.net/2021/12/22/pi-hole-ftl-v5-12-web-v5-9-and-core-v5-7-released
Brief documentation for these warning can be found here:
There is no way to turn off the warnings - they are generated by dnsmasq and Pi-hole shows them all.
To fix it so you no longer get the warning, see this thread:
I read through several Microsoft documentation pages but nothing really helped. Here is what seems to happen: Windows always uses the primary DNS-suffix when asking for a DHCP lease. It simply ignores the connection-specific one. This one is only used when accessing devices over a given connection. Sounds somewhat useless but matches your observation.
The idea could be to add a new file /etc/dnsmasq.d/99-domains.conf and add
domain=CONSULTING-AG.local,192.168.2.123
where the CONSULTING-AG.loc…