-
Notifications
You must be signed in to change notification settings - Fork 30
DNS and pages on gateway #39
Comments
I do like the idea of dnslink for this (esp. combined with IPNS when that is working). The CNAME as root problem is quite real unfortunately. The way I solved it for Neocities custom domain usage was to have the domains set an A record to a re-assignable IP address at AWS running a web server. That server's only purpose is to redirect
This is fairly common practice. Tumblr uses something similar for custom domains. |
Option 4 seems like a good approach. The practice of using non-host |
I do want to allow pure DNS usage of 5. Just TXT
We do not have regular redirection for HTTP, this is for pure DNS + IPFS usage. i would like to have this possibility without forcing
To me, this is a much cleaner thing, but it does make things more complicated. if others feel this is annoying, then i can just suck it up, use |
SGTM! 👍 |
For latency optimization, we might send both DNS queries at once |
f yeah! I've gotta have another swim in the IPFS-for-site-hosting pool |
This shouldn't be closed for now |
I propose to add a DNS record: In order to show that the site can be accessed through a local gateway for this script proxy.pac
Sorry for my google translate |
A few options for pointing custom domains to a gateway,
as discussed on IRC: https://botbot.me/freenode/ipfs/2015-09-03/
Option 4 seems best, option 3 could also work.
Also checkout:
1. CNAME, with TXT on same domain
This won't work, since we can't have CNAME with any other records (TXT in this case.)
2. A/AAAA, with TXT on same domain
This works, but now the gateway IP addresses are part of the "API".
3. CNAME, with TXT another subdomain
problem: example.net inherits all ipfs.io records
4. CNAME
We use a target domain for CNAME, instead of ipfs.io,
so that example.net doesn't inherit anything but A/AAAA records.
The text was updated successfully, but these errors were encountered: