jfb
January 11, 2022, 2:29am
2
The warnings have always existed in /var/log/pihole.log /var/log/pihole-FTL.log
pi-hole:development ← pi-hole:tweak/warning_messages
opened 09:50AM - 13 Nov 21 UTC
**By submitting this pull request, I confirm the following:**
- [X] I have re… ad and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md).
- [X] I have checked that [another pull request](https://github.com/pi-hole/FTL/pulls) for this purpose does not exist.
- [X] I have considered, and confirmed that this submission will be valuable to others.
- [X] I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
- [X] I give this submission freely, and claim no ownership to its content.
**How familiar are you with the codebase?:**
## 10
---
Add DNSMASQ_WARN message type whenever dnsmasq logs a warning. Also do not flush the message table on reload (but only on restart) so that config-related (i.e. one-time) warnings are not accidentally deleted.
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:
https://docs.pi-hole.net/ftldns/dnsmasq_warn/
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…