Check the comments on that public pi-hole link; the guy gives a few "tips" (in the form of a paste of shell commands and apache config changes - so you'll have

Check the comments on that public pi-hole link; the guy gives a few "tips" (in the form of a paste of shell commands and apache config changes - so you'll have to understand all of that) on how to begin to set up your own "public pi-hole" if you don't trust his. The greatest issue seems to be whether your hosting service will allow you set a server up (droplet or raspi host) to be a DNS server; his changes in the paste seem to be to mitigate the issues that could come from allowing it. While I've done my fair share of apache config editing and other sysadmin tasks (for my own hobbyist purposes mainly), I'd still do a ton of research on the changes listed to figure out whether they will do what they're supposed to, and whether there are any other things to apply as well. Lastly - I wonder if you could set this up (on a raspi of course) and let it be public facing on your home network? That is - would say comcast or cox allow it (technically, they don't allow any servers, but I've heard that at least cox tends to "look the other way" for low-bandwidth home-based stuff; I would think a home-based DNS pi-hole server that only you and maybe trusted family/friends use would fall in that category - ymmv)?