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

Feature request: Use DNS instead of random ports #43

Closed
saoron opened this issue May 19, 2022 · 3 comments
Closed

Feature request: Use DNS instead of random ports #43

saoron opened this issue May 19, 2022 · 3 comments

Comments

@saoron
Copy link

saoron commented May 19, 2022

Hi, Thank you for this wonderful project.

It would be great to have all connection go threw a single port and redirected via subdomains (like frp/ngrok).

For example:

xxx.bore.pub
yyy.bore.pub

Thanks,

@ekzhang
Copy link
Owner

ekzhang commented May 19, 2022

Unfortunately resolving based on DNS origin is impossible for TCP, since the origin isn't passed in any request metadata like it is for HTTP. Bore is agnostic to any protocol. It is not aware of HTTP by design. Also subdomains complicate deployment (wildcard DNS entries, TLS certificates). For these reasons this is out-of-scope.

@ekzhang ekzhang closed this as completed May 19, 2022
@orhun
Copy link
Sponsor Contributor

orhun commented May 19, 2022

@saoron check out rathole, it might fit your needs.

@remingm
Copy link

remingm commented Jun 4, 2022

@saoron It looks like boringproxy.io might do what you want.

https://github.com/boringproxy/boringproxy

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

4 participants