ipfs
Create & manage OpenNIC TLD for IPFS website hosting
Checklist
- [X] My issue is specific & actionable.
- [X] I am not suggesting a protocol enhancement.
- [X] I have searched on the issue tracker for my issue.
Description
OpenNIC project requirements are here. I think the largest obstacle of hosting IPFS website is buying domain. OpenNIC domains are totally free and very easy to add new domain.
Kubo already supports using OpenNIC TLDs (opt-in via DNS.Resolvers configuration).
I understand you are suggesting setting up custom TLD at OpenNIC, and ensuring it a resolver for that TLD is enabled by default (like ENS).
@matyapiro31 any thoughts on how such integration could look like?
Namely:
- How new domains are registered?
- How things like domain squatting are solved?
- What are use cases?
- What is the value added when compared to ENS or ICANN?
I understand you are suggesting setting up custom TLD at OpenNIC, and ensuring it a resolver for that TLD is enabled by default (like ENS).
It's correct.
How OpenNIC project accepts new TLD is written here.
What we need the most is authoritative DNS server working for 24hs. Next is domain registering system.
Why creating new OpenNIC domain?
Because it's free and perfectly under our control, so adding new domain from ipfs commands automatically, no cost, no personal information is enabled by new TLD.