grimd

I have been managed for years a cluster of recursive authoritative DNS cluster for a broadband ISP (around 30k subscribers). We have also 2 authoritative DNS servers running bind, but the operations were fully automated through a bunch of custom python scripts (the NOC operators can request a new record by themselves). For the recursives one, I started with bind, but after a few months I replaced it to unbound and it's works like a charm. The only problem that I experienced was about DDoS, mainly generated by ultra cheap chineses home router with buggy firmware. Anyway after a few attacks, we start implementing an application monitoring solution and we were able to mitigate the attacks in a short time. On my laptop I run a a docker container with grimd (https://github.com/looterz/grimd) as recursive DNS and DoH proxy. I can filter out lot

Found it: https://github.com/looterz/grimd Questions: 1) is this black hole concept sustainable? Or, does it require significant management, and is likely to be circumvented by serving content through a proxy anyway? 2) Why do you run this on the cloud? Don’t you then incur significant bandwidth costs? Or, if DNS only are there speed issues with your EC2 instance lagging?

I don't know if storing a plain text log of my browsing history is a good thing or not... https://github.com/looterz/grimd/blob/fc327b2f2993f762c8557c...

https://github.com/looterz/grimd Is a golang ad-hole. I've found it to be more performant in both the DNS/server and UI