I started my pihole's DHCP server, disabled router's one. Added a lot of new blacklists, the dashboard shows an enormous quantity of sites blocked but wherever I go - each website has so many ads like there is no tomorrow.
I was so excited about this little thing...
Ads being blocked.
Not a single one is blocked, all visible.
0blmk8de1u
Your debug log shows that your Pi-hole is working correctly and in the past 24 hours has received and processed DNS queries from 11 clients:
[2020-05-05 14:59:47.185 16435] Imported 5517 queries from the long-term database
[2020-05-05 14:59:47.186 16435] -> Total DNS queries: 5517
[2020-05-05 14:59:47.186 16435] -> Cached DNS queries: 737
[2020-05-05 14:59:47.186 16435] -> Forwarded DNS queries: 2612
[2020-05-05 14:59:47.186 16435] -> Exactly blocked DNS queries: 2168
[2020-05-05 14:59:47.187 16435] -> Unknown DNS queries: 0
[2020-05-05 14:59:47.187 16435] -> Unique domains: 998
[2020-05-05 14:59:47.187 16435] -> Unique clients: 11
[2020-05-05 14:59:47.188 16435] -> Known forward destinations: 6
From a client that you believe should be connected to the Pi-Hole for DNS (and where you are seeing ads), from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of
nslookup pi.hole
Thanks for the quick reply, really appreciate it!
Here is the output:
Server: pihole
Address: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
Name: pi.hole
Addresses: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
192.168.0.88
Now let's test the blocking:
nslookup flurry.com
Server: pihole
Address: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
Non-authoritative answer:
Name: flurry.com
Addresses: ::
212.82.100.153
74.6.136.153
98.136.103.26
These entries in your gravity log are malformed. I don't think they were imported from any of your blocklists, so it appears they may have been entered manually:
-rw-r--r-- 1 root root 5989384 May 5 15:01 /etc/pihole/gravity.list
-----head of gravity.list------
(^|\.)adform\.net$
(^|\.)adocean\.(pl)$
(^|\.)adsbtrack\.com$
(^|\.)adserver\.snapads\.com$
It's very probable- it's my first day with the device. Tried everything before writing here.
What would you recommend to fix the above?
Run this command from the Pi terminal. Then run a new debug log, upload it and post the new token.
pihole -g -f
Did all that as requested, here is the link : https://tricorder.pi-hole.net/fvjr64kjbv
You still have the malformed entries. I'm looking to see where they are coming from:
*** [ DIAGNOSING ]: Gravity list
-rw-r--r-- 1 root root 5989402 May 5 16:25 /etc/pihole/gravity.list
-----head of gravity.list------
(^|\.)adform\.net$
(^|\.)adocean\.(pl)$
(^|\.)adsbtrack\.com$
(^|\.)adserver\.snapads\.com$
Let's eliminate some potential problems for now. Revert back to the stock blocklists, and then rebuild gravity and generate a new debug token. This is a known good configuration of the gravity list.
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
http://sysctl.org/cameleon/hosts
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
Done 
Fresh debug output: https://tricorder.pi-hole.net/s9djwre097
Now, from the connected client, re-run the nslookup commands you ran earlier.
nslookup pi.hole
nslookup flurry.com
C:\Users\Mike>nslookup pi.hole
Server: pihole
Address: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
Name: pi.hole
Addresses: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
192.168.0.88
C:\Users\Mike>nslookup flurry.com
Server: pihole
Address: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
Non-authoritative answer:
Name: flurry.com
Addresses: ::
74.6.136.153
212.82.100.153
98.136.103.26
Update:
Ads are still shown, but setting pihole as DNS (as it was set from the beginning) now causes a huge internet lag.
Just to be sure its pihole-FTL thats answering, what does below output on that Windows client ?
nslookup -class=chaos -type=txt version.bind
EDIT: ow and while at it, what upstream servers are configured ?
nslookup -class=chaos -type=txt servers.bind
nslookup -class=chaos -type=txt version.bind
Server: pihole
Address: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
version.bind text =
"dnsmasq-pi-hole-2.80"
C:\Users\Mike>nslookup -class=chaos -type=txt servers.bind
Server: pihole
Address: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
servers.bind text =
"208.67.220.220#53 45 2"
"208.67.222.222#53 166 2"
And what does below now display after you have defaulted the blocklists ?
nslookup flurry.com
Server: pihole
Address: 2a02:a317:e244:b580:18c1:f8cd:1da:e3fb
Non-authoritative answer:
Name: flurry.com
Addresses: ::
98.136.103.26
212.82.100.153
74.6.136.153
Do you have any whitelist or blacklist entries ?
Try clear them too.
Run Pi-hole as default as possible.
EDIT: This how should look like:
C:\>nslookup flurry.com
Server: phb5.dehakkelaar.nl
Address: 10.0.0.4
Name: flurry.com
Addresses: ::
0.0.0.0
I'm afraid I already did when @jfb asked me to. 
Here is the newest debug output: https://tricorder.pi-hole.net/h5q10ovu7y