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
experimental DNSLINK support doesn't work with /ipns/ path #288
Comments
For a little background, browser extension uses Basic troubleshooting is to check if both public and your local gateway return the same result: Right now both return this error for your FQDN:
It looks like the source of problem is IPNS path in your dnslink (most of sites use static IPFS path). cc @Kubuxu |
Based on the example: https://github.com/ipfs/examples/tree/master/examples/websites it seems an IPNS path in my dnslink was at least intended to work at some point. It works on the command line:
but only if I pass in the
So...should I file a bug on go-ipfs do you think? |
I wonder if the api doesn't recurse by default, reminds me of: ipfs/kubo#4167 |
|
Fix from ipfs/kubo#4293 (comment) will be introduced when #558 is merged. |
I have a DNS TXT entry for ggr.com:
Yet, when I visit https://ggr.com using Firefox 56.0 on OpenBSD 6.1-stable-amd64 with ipfs-companion 0.4.11-dev I am NOT redirected to the IPFS version of the site as I had hoped/expected I would be.
I have HSTS enabled on ggr.com. I have more than one TXT DNS entry. I wonder if one of those is causing problems. In any case, even though its an experimental feature, I figured a 100% repro example problem case might be useful.
The text was updated successfully, but these errors were encountered: