As you noted, whitelisting is global, for all clients using the Pi-Hole.
A third option is to have an additional Pi-Hole (on a Pi, VM, etc) and put a subset of computers on that. You can tailor the blocking to those computers.
At home, I have a Pi-Hole that serves my wife's devices and it has blocklists and whitelists that work for her. My computers are on a different Pi-Hole with different lists and options.
If you are dealing with just a few domains, you could put the IP addresses in the /etc/hosts file on the client computer, and they would resolve locally before going to the Pi-Hole.
Thank you for your reply. Your idea is very good. But I do not want to work with multiple instances of pi-hole at the same time. This increases the dependencies unnecessarily and makes my job as an admin harder. I had hoped for an easy solution. If there are no other solutions, I'll start a feature quest. Maybe that's a function that others would like to have. Thank you for the great support and the ingenious program.
Hello,
great. Then I do not need to write a request anymore. But I do not understand what happened to it. He is closed and I can not vote for it. However, the problem was not solved in the current pi-hole version. How was the problem solved? Is the only solution still to use multiple pi-hole instances?
Many Greetings
PS: I hope my english is good enough. Unfortunately, I have to use Google Translator.