Device not respecting DNS Director or (Yaz)DHCP Server settings

[dangkhoa]

I have an Intel NUC running Pi-hole that I'm currently using as my DNS server for my network:

I have a device on my IoT network that's pretty chatty (a baby monitor), and it regularly causes my Pi-hole to throw a warning that the concurrent DNS query limit is reached. I've tried both of the following, and I still see in my Pi-hole logs that the device is making DNS requests to my Pi-hole rather than the DNS server I've set for it (1.1.1.1):

• Make a DHCP reservation and set the DNS server for this device, on the DHCP Server tab:
  • 

• Using DNS Director, set the redirect to 1.1.1.1:
  • 

I could use some help figuring out if this is an issue with my DHCP server settings, DNS Director settings, Pi-hole settings, or the device in question... (note, the baby monitor does not have the ability to configure its own DNS server - it's supposed to use whatever the router advertises as the DNS..)

Configuration: RT-AX56U, running AsusWRT-Merlin 3004.388.10_2, with YazDHCP 1.2.4.

 

[bennor]

To start with, how is your router configured for Pi-Hole? Do you have the Pi-Hole in the WAN DNS fields? If you do they should be in the LAN DHCP Server DNS fields instead.

Post Edit. There are various other discussions on how to setup Pi-Hole to work with an Asus router.
Post more information about your setup.
What is your router's IP address range?
Are you using YazFi?
How is the router configured to use Pi-Hole?
Is the Pi-Hole set to No Redirection in DNS Director?

 

[bennor]

Configuration: RT-AX56U, running AsusWRT-Merlin 3004.388.10_2, with YazDHCP 1.2.4.

Also, what specific router and firmware are you running? You indicate an RT-AX56U with 3004.388.10_2, however the last Asus-Merlin firmware for the RT-AX56U is 3004_388.8_4 according to the Asus-Merlin website and download page.