Edit: Resolved. I deleted the MAC address entry from the client list and added by IP and it started working. I'll leave the original post, but without any of these devices restarting and no device changes I'm not sure what would have caused this.
==
Not exactly sure when this started getting blocked, but I've used this configuration for a bit on v6 without noticing an issue. Other whitelisted devices and domains (which seem to be added as IP rather than MAC) seem to be working as expected.
- Device is in group "IOT"
- Domain is on whitelist for group IOT
- A Regex to block non whitelisted domains is assigned to IOT.
Expected:
Domain is allowed.
Actual:
Domain is blocked.
Without a debug log it's almost impossible to know what was happening with your rules, but reading your solution it seems:
- you configured a block regex rule and a whitelist rule;
- the whitelist rule was assigned to a MAC address, but Pi-hole was not able to identify the device MAC address.
- Without the MAC address, the whitelist was never applied.
Note that DNS uses IP and Pi-hole uses other methods to identify the MAC address when it is possible.
MAC addresses are only visible in the immediate vicinity of your Pi-hole (it won't work across routers, VLANs, etc.)
Thanks. It's probably too late to generate the debug token now that I've made changes. Understand the limitations of the mac address, none of those should impact my setup, it's pretty flat without much complexity.
I'm mostly confused as what could have caused it, I've ran this configuration for over a year, if not longer. I suppose I can't say this hasn't happened before and I've just not noticed it.
Appreciate the reply though. I'll grab a debug token next time before I make changes.
