But for some reason, it is not working and I assume that the format of my blocklist is incorrect, For example, if I ping surviv.io, I see in /var/log/pihole.log:
Jan 30 08:24:44 dnsmasq[3866]: query[A] surviv.io from 192.168.1.11
Jan 30 08:24:44 dnsmasq[3866]: forwarded surviv.io to 208.67.222.222
Jan 30 08:24:44 dnsmasq[3866]: query[AAAA] surviv.io from 192.168.1.11
Jan 30 08:24:44 dnsmasq[3866]: forwarded surviv.io to 208.67.222.222
Jan 30 08:24:44 dnsmasq[3866]: reply surviv.io is 104.17.61.91
Jan 30 08:24:44 dnsmasq[3866]: reply surviv.io is 104.16.118.94
Jan 30 08:24:44 dnsmasq[3866]: reply surviv.io is 2606:4700::6810:765e
Jan 30 08:24:44 dnsmasq[3866]: reply surviv.io is 2606:4700::6811:3d5b
Jan 30 08:29:55 dnsmasq[3866]: query[A] quantummetric.com from 192.168.1.11
Jan 30 08:29:55 dnsmasq[3866]: gravity blocked quantummetric.com is 0.0.0.0
Jan 30 08:29:55 dnsmasq[3866]: query[AAAA] quantummetric.com from 192.168.1.11
Jan 30 08:29:55 dnsmasq[3866]: gravity blocked quantummetric.com is ::
You have this blocklist assigned to group 1 (gaming), but there are no clients assigned to that group. As a result, the blocklist is not applied to any clients.
It's optional. Many public blocklists are used as native hosts files, and this requires an IP mapping. The NULL IP leads to nowhere and is commonly used here to block domains.
Pi-hole strips out any leading IP's and just keeps the domains. So, if you are using your list for Pi-hole only, you can omit the leading IP's, but this is not required. Pi-hole will remove them.
So there's something that is still not working. I have pd.na.a.pvp.net and pd.na.a.pvp.net.cdn.cloudflare.net in my blocklist and it seems to still be forwarding these requests.
Jan 31 10:22:47 dnsmasq[3866]: query[AAAA] pd.na.a.pvp.net from 192.168.1.66
Jan 31 10:22:47 dnsmasq[3866]: forwarded pd.na.a.pvp.net to 208.67.222.222
Jan 31 10:22:47 dnsmasq[3866]: reply pd.na.a.pvp.net is <CNAME>
Jan 31 10:22:47 dnsmasq[3866]: reply pd.na.a.pvp.net.cdn.cloudflare.net is NODATA-IPv6