Please ensure that you are running the latest version of the beta code.
Current Pi-hole version is v4.3.2-389-g10c2dad
Current AdminLTE version is v4.3.2-357-g3cac308e
Current FTL version is vDev-9889501
Run pihole -up to update to the latest, then verify that the problem still exists before reporting it.
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[i] Warning: You are using FTL from a custom branch (release/v5.0) and might be missing future releases.
[✓] Everything is up to date!
Problem with Beta 5.0:
Added client to configured clients
Created a new group
No lists added to group
Added client to only the empty group
This is how I understand how this is done.
Domains are still being blocked. Am I forgetting something?
In group assignment, make sure "Unassociated" is unchecked. Check the name of the group you created in the groups tab. Make sure it is the only one checked. Unassociated is a catch-all for all new ip's discovered and by default is part of the pihole filtering.
Checked that once again. As I did before.
When @Ronnick replied I switched to the empty group again.
Still blocking domains. To check that I used the query log.
Today I had to login again while I checked '7 day box'. Not closed the browser in the meanwhile.
I know there is another topic about that. I'm now searching where FF (72 on Linux) stores cookies.
Maybe related, maybe not. Just letting you know.
Grouping doesn't work for me too. When I'm trying to group domains, they are not blocked anymore. The only solution is to leave everything in the same group that was migrated together with the blocking lists (gravity).
Client grouping isn't possible too:
I see only single adresses in the list. The second problem is: I have clients with privacy extensions for IPv6. So after a period of time a client has a new temporary IPv6 address (ULA or GUA). At the moment Pihole seems to be unable to get all (new) addresses of one device together. The network table doesn't show hostnames, so i think there is something wrong with the detection of clients adresses.
Now turned pihole back on by editing Groups but still see the ad on the same site in the same FF profile.
Ctrl+F5 did not help. Neither did clearing cache or restart FF profile. nslookup returns ** server can't find scorebordresearch.com: NXDOMAIN
on client as well on pihole
Prepared a screenshot to illustrate my point. After that I tried again and the ad is blocked. I'm lost. I can't explain this.
When I use FF to visit scorebordresearch.com or sb.scorebordresearch.com it's being blocked I guess (NXDOMAIN) but it does not show up in Query Log. Again, I'm lost and thinking of restarting Pihole but that doesn't help debugging...
Edit: scorebordresearch.com does show up in Long term data but in green (OK farwarded).
AFAIK it should be on a block list. How can I check? It is not on the 'Blacklist' which are only mannually added domains, right?
Edit: Used sqlite to see what's in gravity.db. I was wrong, scorebordresearch.com wasn't on any list.
Edit: Put domain on blacklist: (^|\.)scoreboardresearch\.com$
Does not show in Query Log or Long term data Query Log after pihole restartdns.
My pihole installation does show hostnames after using 'Settings -> DNS - > Use Conditional Forwarding'.
'IP of your router' I set to IP address of my internal DNS server that only handles my local domain.
'Local domain name' I set to local domain name (i.e. xyz.local)
Really? Hm. Conditional Forwarding is active but my Pihole does not. I also tried to have the Pihole als DHCP server to get this fixed, but got the same result. Maybe the OS makes a mistake. It's Dietpi 6.28.0.
Appendix:
I found it. Why ever in the /var/chache/unbound/resolvconf_resolvers.conf the routers address was the wrong (the default one that is active when resetting it). Corrected and now arp shows hostnames and Pihole is recollecting hosts informations. We'll see if Client Grouping will became functional now.
At this place one thing that can lead to the illusion of an unexpected behavior: DNS-Caching.
When experimenting with the new group managing there is a need to flush the systems DNS cache after every step or complete disable DNS-caching.
Unfortunally i.e. Firefox caches DNS too! So this should be completely disabled via about:config.
I am experiencing the same issue: Any attempt to group either a single or all IPs results in Pi-hole bypassing all exact and regex blacklists (but not Gravity lists) for all client(s) regardless of Group/Domain assignment(s).
Add Group(s)
Add Client(s). Add Client(s) to Group(s)
Add Group(s) to Domain(s) as required
Restartdns (via web panel or command line)
Exact and regex blacklists are bypassed
Most IPs are statically assigned. Everything should be working on a per-client basis, but it is not. Ungrouping results in all black and whitelists being adhered to (expected behavior).
