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

stub-first fails with stub-tls-upstream #68

Open
isbear opened this issue Aug 23, 2019 · 1 comment
Open

stub-first fails with stub-tls-upstream #68

isbear opened this issue Aug 23, 2019 · 1 comment
Assignees

Comments

@isbear
Copy link

isbear commented Aug 23, 2019

Hello.

When both stub-first and stub-tls-upstream options are enabled, unbound tries to use parent NS, but it uses TLS with them, while accessing them on the default port (53). I think it should either not use TLS on parent NS in this case, make it configurable, use tls-port, or document that this use case will fail.

@ralphdolmans ralphdolmans self-assigned this Aug 26, 2019
@isbear
Copy link
Author

isbear commented Jan 14, 2020

As it turns out, I am slightly wrong here. It works, for the first query only. Then it fails for every query, that is not in the cache.
It seems, that first query on fallback sets it's iq->dp here:

if(!prime_root(qstate, iq, id, iq->qchase.qclass))

All subsequent queries on fallback set their iq->dp here:
if(prime_stub(qstate, iq, id, delname, iq->qchase.qclass)) {

In the first case copied value of dp->ssl_upstream is false, in second case it is true.
I still know too little to really understand, what all of this code does, but maybe it will help others to pinpoint the problem.
Edits: grammar

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

2 participants