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

Support for dnslink #98

Open
agazso opened this issue Jan 26, 2022 · 2 comments · May be fixed by #408
Open

Support for dnslink #98

agazso opened this issue Jan 26, 2022 · 2 comments · May be fixed by #408
Assignees
@luissanchez0305
Labels
enhancement New feature or request issue

Comments

@agazso
Copy link
Member

agazso commented Jan 26, 2022

Currently Bee (and the gateway-proxy) only supports ENS domains. The issue with those are that it's quite expensive to buy them but more importantly it's also quite expensive to update or modify them because of mainnet gas prices.

One idea is to support dnslink on the gateway-proxy, at least to some degree. For example if the proxy served unknown A records by looking up their dnslink TXT record then it classic DNS domains could still work but the content could be served through the proxy.
@agazso agazso added the enhancement New feature or request label Jan 26, 2022
@bee-runner bee-runner bot added the issue label Jan 26, 2022
This was referenced Nov 11, 2022
Closed
Open
@agazso
Copy link
Member Author

agazso commented Nov 14, 2022

The specification of the configuration as per our meeting is the following:

There is a configuration variable called DNSLINK which is a boolean and defaults to false. When this is enabled then there is another configuration variable called DNSLINK_ALLOWED_DOMAINS which defaults to undefined or it can be a comma separated string and it contains a list of allowed domains. When there are no domains specified it tries to serve any kind of domain that it receives in the Host header of the HTTP request. Otherwise the gateway-proxy would first check if the Host header in the request matches and of the domains in the list (if not then 403) and serve that.

The feature works as a complementary feature to the CID_SUBDOMAIN and ENS_SUBDOMAIN features.

@luissanchez0305
Copy link
Contributor

luissanchez0305 commented Nov 15, 2022 •
edited
Loading

@agazso 1 question: If the Request is going to response 403 status, then that's the end of the request.
How would DNSLINK feature complement the CID and ENS if the request had ended at that point?

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

@luissanchez0305 luissanchez0305

Labels
enhancement New feature or request issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: dnslink support ethersphere/gateway-proxy
Feat/dnslink support ethersphere/gateway-proxy
2 participants
@agazso @luissanchez0305