On a technical level you could blackhole any DNS request on that network by running your own recursive resolver (i use unbound) and using these DHCP options which is about the best you can do for HTTPS as best I can tell (I wanted to do something similar to this but couldn’t get further than that). Then you could redirect every domain resolution to 65.109.101.238 (marxists.org currently), but I lack the knowledge on how to make anything in the URLPath portion properly resolve. Like example.com/where-to-buy-a-tent would just be rendered up as 65.109.101.238/where-to-buy-a-tent.
(If anyone was wondering and wants to help bridge the gap in my knowledge I wanted to make resolve to old. automatically without a browser plugin on all devices but that isn’t at the DNS level.)
On a technical level you could blackhole any DNS request on that network by running your own recursive resolver (i use unbound) and using these DHCP options
which is about the best you can do for HTTPS as best I can tell (I wanted to do something similar to this but couldn’t get further than that). Then you could redirect every domain resolution to
65.109.101.238(marxists.org currently), but I lack the knowledge on how to make anything in theURLPathportion properly resolve. Likeexample.com/where-to-buy-a-tentwould just be rendered up as65.109.101.238/where-to-buy-a-tent.(If anyone was wondering and wants to help bridge the gap in my knowledge I wanted to make
resolve to old.
automatically without a browser plugin on all devices but that isn’t at the DNS level.)