DNSMASQ blocks desired domain for work PC

[thedarkparadox]

Problem Description

I currently have Pi-hole acting as both DNS and DHCP server. Works beautifully. However, my work computer is trying to pull its own Connection-specific DNS Suffix, which was blocked by the DNSMASQ causing me to receive the following warning:

Ignoring domain CONFIG_DOMAIN for DHCP host name HOSTNAME

I've read through various documentation and forums, including here, trying to find a method of allowing this one computer to obtain the correct domain rather than what I have set in Pi-hole, but just can't wrap my head around getting it set correctly.
Any help is greatly appreciated.

Attempted fixes

• Creating file named 99-domains.conf and placing it in /etc/dnsmasq.d containing domain=ad.local,192.168.1.xxx, replacing xxx with actual local IP address obviously.
• Changing Interface settings from Allow only local requests to Respond only on interface ens192.

Expected Behaviour:

• Pi-hole v5.15.5
• FTL v5.21
• Web Interface v5.18.4

Wanting PC to receive its intended domain ad.local rather than the domain handed out by Pi-hole.

Actual Behaviour:

Receives domain handed out by Pi-hole.

Debug Token:

https://tricorder.pi-hole.net/0hxwGohx/

[jfb]

Take a look here:

Ignoring domain CONFIG_DOMAIN for DHCP host name HOSTNAME

Same problem here. I generated a debug log. Token: https://tricorder.pi-hole.net/ctq25uyd/ Maybe a developer knows how to fix that. It's the laptop of my company. Seems like everything is working fine. If the reason for the warnings cannot be eliminated, is there maybe a way to just disable the warnings or just the large warning sign in the dash? [ipconfig] [warnings]

[thedarkparadox]

Thank you kindly for the speedy response. Only step I was missing was to restart the DNS resolver on Pi-hole. It's now working as intended. Have a terrific weekend!