ipfs / ipfs/specs

Add DNSLink specs for resolving /ipns/{fqdn} content paths

Open
#389 0 comments 0 reactions 0 assignees View on GitHub
dif/medium kind/missing-specs P1
Dominant language
HTML
Stars
1.2k
Forks
247
Avg merge
5d 21h
Merged PRs (30d)
4

Description

We have a dedicated https://dnslink.dev website with loose specification, but it lacks necessary maintenance and love.
It is also written from IPFS-agnostic perspective, and does not go too deep into how `/ipns/{fqdn}` and `/dnslink/{fqdn}` resolution should work in IPFS ecosystem specifically. Due to this, our stack still only supports the former, and the latter can't be used, blocking people from using DNSLink for more than just IPFS.

Given how important DNSLink is for IPFS ecosystem, we should write proper spec that describes how `/ipns/{fqdn}` should be resolved and add it to https://specs.ipfs.tech. This way we close the specification gap, and have specs for all identifier types on `/ipns/` namespace.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.