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

SNI routing based on wildcard domains #373

Closed
yrutschle opened this issue Dec 31, 2022 · 2 comments
Closed

SNI routing based on wildcard domains #373

yrutschle opened this issue Dec 31, 2022 · 2 comments

Comments

@yrutschle
Copy link
Owner

    Would be interesting if it is possible to do SNI routing based on wildcard domains, like sending all requests with example.com or *.example.com to one server.

I was trying to do the same with my OPNsense router and it seems impossible to configure that way.

Originally posted by @poVoq in #350 (comment)

@yrutschle
Copy link
Owner Author

yes, but for next version :-)
thanks for the suggestion

@yrutschle
Copy link
Owner Author

actually it does seem to work, the SNI matching uses glob (shell) matching so this:

protocols: (
[...]
 { name: "tls"; sni_hostnames: [ "*.example.org"]; host: "localhost"; port: "443"; },
[...]
);

does what you would expect. Obviously this becomes a catch-all for that domain, so if you have other forwarding targets for more specific sub-domains, they need to come first.

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

No branches or pull requests

1 participant