Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Specify secure transport requirement for certain authoritative servers #1215

Open
bdaehlie opened this issue Jan 10, 2025 · 2 comments
Open

Comments

@bdaehlie
Copy link

Let's Encrypt would like to be able to provide Unbound with a list of authoritative DNS servers (in domain and IP address formats) and then require a specified secure transport protocol (e.g. DoH or DoQ) to be used whenever recursive resolution runs across one of those servers.

@Aura67
Copy link

Aura67 commented Jan 10, 2025

@gthess
Copy link
Member

gthess commented Jan 17, 2025

@bdaehlie, for upstream, Unbound only supports DoT at the moment which can also be configured per upstream.

If you are talking to forwarders, forward-zone needs to be configured and the relative option is forward-tls-upstream as pointed out by @Aura67 .

If you are talking to authoritatives, stub-zone needs to be configured and the relative option is stub-tls-upstream.

You can also use stub-no-cache/forward-no-cache to always ask for fresh records.

For DoT to work you would need to configure tls-cert-bundle as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants