Thank you for your reply.
First: I found out what I did wrong. I had disabled forwarding in Unbound, thinking that it would forward all my requests to the upstream dns at once, without looking in the cache. Turns out "forwarding" just means "disable recursion". No idea why they would not just name it disable recursion :?
As for your setup: I think in the future I will need to configure a dnssec server for Mozilla or Windows. As for Chrome: I am guessing Google is going to do all to use their DNS servers in there. That's why they are using dns over https: way harder to block and filter, thus generating more data for them.
OPNDns actually supports dnssec, so I would hope that is what's used when I configure it in OPNSense? As for my isp looking in: I really don't mind that much. I want to spread my data, so that there is not ONE source that knows everything about me (Google). A few others that have data that they are mostly not allowed to use does not bother me that much :)
First: I found out what I did wrong. I had disabled forwarding in Unbound, thinking that it would forward all my requests to the upstream dns at once, without looking in the cache. Turns out "forwarding" just means "disable recursion". No idea why they would not just name it disable recursion :?
As for your setup: I think in the future I will need to configure a dnssec server for Mozilla or Windows. As for Chrome: I am guessing Google is going to do all to use their DNS servers in there. That's why they are using dns over https: way harder to block and filter, thus generating more data for them.
OPNDns actually supports dnssec, so I would hope that is what's used when I configure it in OPNSense? As for my isp looking in: I really don't mind that much. I want to spread my data, so that there is not ONE source that knows everything about me (Google). A few others that have data that they are mostly not allowed to use does not bother me that much :)