DNSMASQ_WARN with vpn after update

[Mathew_Green]

Hi there since I updated to the most recent version I'm receiving this error Messages.

DNSMASQ_WARN Warning in dnsmasq core:
Ignoring domain $company_domain for DHCP host name $company_pc_hostname

Of course these variables are text in my logs. How can I prevent Pi Hole from ignoring this domain. It only happens with my companies pc. If I use my private Devices without VPN it works okay.

Details about my system:
PiHole on Raspberry Pi4B 4GB
Unifiy Switch + AP
Lenovo Laptop from Work is connected via wifi
5G Mobile router for Internet connectivity

What I have changed since installing Pi-hole:
permitted all origins (DNS Settings)
enabled rapid commit and ipv6 (had to)

[jfb]

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.

Add dnsmasq warnings to message table

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/

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

[Mathew_Green]

Hey there,
okay so it wouldn't help to go back.
Here is the link:
https://tricorder.pi-hole.net/tYHhR0Xt/

[NGr]

Hi,

This post may be helpful for you:

Ignoring domain CONFIG_DOMAIN for DHCP host name HOSTNAME

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…

[Mathew_Green]

Thx, that solved the problem partially. However, it only seems to solve the Problem if I only use ipv4. In my configuration ipv6 is enabled. So every 30 Minutes or so the error appears again.

[NGr]

You might be able to add the IPv6 address to that file, but I don't know what the correct syntax would be.

[Mathew_Green]

I changed the domain name in pi hole for all of my devices to the name of my working machine. Brutal but as I work for one company only a feasible solution. Seems to fix this issue and we can close this topic.

[Cornishman]

I had the same issue and had to add the IPv6 addresses. The format I used was the IP address reported in the "Currently active DHCP leases" page within the pi-hole admin web page under the Settings menu DHCP tab page. There is an "IP Address" column that provides the necessary entry with the necessary format (the format I used was the ":" separated groups of 3-4 hex digits which I used to replace the IPv4 field with the "." separators).