Not true. Please don't spout nonsense here.

Glad to see you got it working, I believe the reason pihole is occasionally not used is due to the delay from a first time lookup on the pi. Once it is cached in pihole it will probably beat...

@lukass2000 Based on this result, I want to make sure the Pi is on 192.168.10.200? In this response the DNS query was answered by 192.168.10.5 In the meantime, from the site dashboard, follow these...

@lukass2000 Sorry, I mistyped. The command was supposed to be: dig @192.168.10.200 google.com The @ means it will send the dns to the ip of your pihole. And yes, the cache is enabled on your instance...

On your lan, you can go to http://pi.hole/admin/api.php?getCacheInfo This will show a string of the cache info, at the start of it, there will be something around the lines of...

@lukass2000 I run it as both a pi3b (primary dns) and proxmox container (secondary dns). Does your pihole have caching enabled? Responses from the pi should be much quicker once the pi grabs the...