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.

Sign up for GitHub

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

Jump to bottom

"forward-host" do NOT support TLS upstream #546

Closed
liheng562653799 opened this issue Sep 30, 2021 · 1 comment · Fixed by #617
Closed

"forward-host" do NOT support TLS upstream #546

liheng562653799 opened this issue Sep 30, 2021 · 1 comment · Fixed by #617
Assignees
@gthess

Comments

@liheng562653799
Copy link
Contributor

According to my viewing of code and experiments, "forward-host" config item dont support TLS.
SUPPORT: forward-host: 1.1.1.1@853#one.one.one.one
NOT SUPPORT: forward-host:one.one.one.one@853#one.one.one.one

If I am right, can you please tell me are there any reasons why "forward-host" dont support TLS.
Or it is just to be done to support more features that are less important like this; and if so, do we have any plan to support this?
gthess added a commit that referenced this issue Feb 1, 2022
@gthess
- Update stub/forward-host notation to accept port and tls-auth-name.
814a234 
  Fixes #546.
@gthess gthess mentioned this issue Feb 1, 2022
Merged
@gthess gthess self-assigned this Feb 2, 2022
@gthess
Copy link
Member

gthess commented Feb 2, 2022

This should now be supported, thanks for bringing it up!
Btw, when using forward-host beware of the cycle dependency of resolving the name that you use there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gthess gthess

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update stub/forward-host notation to accept port and tls-auth-name NLnetLabs/unbound
2 participants
@gthess @liheng562653799