Perhaps you could configure more than unbound service behind a loadbalancer. Each unbound instance is configured to use different upstream dns servers.
Double check if unbound doesn’t allow you to randomly hop between dns upstreams first, but the above solution should work if that’s unavailable atm.
Is it possible to get unbound to talk to the root servers via TLS/HTTPS by now?
I’m currently using Quad9 because they support DNS over TLS and DNS over HTTPS.
Yes its possible 👍
Use:
forward-zone: forward-addr: 9.9.9.9@853#dns.quad9.netThat is what I’m doing currently but now unbound doesn’t talk to the root servers anymore, it sends all queries to Quad9.
Both scenarios are not ideal because you always end up with one entity knowing all your queries.
Perhaps you could configure more than unbound service behind a loadbalancer. Each unbound instance is configured to use different upstream dns servers.
Double check if unbound doesn’t allow you to randomly hop between dns upstreams first, but the above solution should work if that’s unavailable atm.