I was able to set up UDP 53 running
But why is it not blocking ads.
Ad blocking is enabled
2022-10-10
11:17:36 LOAD Long-term load (15min avg) larger than number of processors: 4.9 > 4
This may slow down DNS resolution and can cause bottlenecks.
Showing in the diagnostic section
Good - that means port 53 is free now.
Restarting your Pi-hole container with the correct port mappings for 53 UDP and TCP should have worked then, and obviously, it did. 
You have to configure your network to make use of Pi-hole, see Post-Install - Pi-hole documentation.
You can verify if blocking is operational by running the following commands from a client that's using Pi-hole for DNS:
nslookup pi.hole
nslookup flurry.com
The latter should result in a 0.0.0.0 reply.
System load is reported as is via the underlying OS.
If you run Pi-hole in a virtualised environment, the reported details may not be accurate, see also e.g. High Load in docker on Synology.
Yes nslookup is replying via 0.0.0.0.
I have only opened port 53 UDP not tcp
The nslookup is working on pc only but not on Android. On Android it is returning 8.8.8.8 but i have added both dns 1 and 2 as the pihole
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.