IPNS over DNS

[hugomrdias]

This is a meta-issue to track progress about IPNS over DNS work.

Goals:

1. deploy production ready nameservers
2. merge final ipns router with support for online and local/offline use-cases
3. interop between js and go

Tasks:

• HTTP Gateway supports /ipns/ namespace feat: add HTTP Gateway support for /ipns/ paths  #2020
• make name resolverecursive by default to follow go-ipfs
• ipfs name resolve should support /ipns/<fqdn> feat: add support for ipns name resolve /ipns/<fqdn> #2002
• implement dns resolver
• ipfs resolve should support /ipns/<fqdn> feat: add support for ipns and recursive to ipfs resolve #2297
• make resolve recursive by default to follow go-ipfs feat: add support for ipns and recursive to ipfs resolve #2297
  ipfs name resolve with recursive default to true makes name-pubsub fail #2001
• ipfs dns should use DNS over HTTPS Support DNS over HTTPS #2212
  • make dns recursive by default to follow go-ipfs
• Merge dns and local router [WIP] experimental routers to make ipns faster #2201
• proper deployment of the nameservers with a safe store for the records
• support CID v1 in ipns paths
• Extract ipns code to a separate package
• Improve the spec Improve IPNS spec specs#205
• finish the RFC following https://github.com/ipfs/RFC/compare/rfc/5-ipns-over-dns
• support cid v1 in subdomain ?? /cc @lidel IPNS: should work with case-insensitive identifiers (Base32) kubo#5287

References:
ipfs/specs#198
#1918
ipfs/kubo#5287

[lidel]

I'm dropping some notes about DNS over HTTPS:

• Binary DNS Queries over HTTPS (DoH): https://tools.ietf.org/html/rfc8484
  (same binary payload format as in regular UDP-based DNS, well understood)
  • good primer on how application/dns-message looks on HTTP https://developers.cloudflare.com/1.1.1.1/dns-over-https/wireformat/
  • https://wiki.mozilla.org/Trusted_Recursive_Resolver
    • DoH endpoint used by Firefox: https://mozilla.cloudflare-dns.com/dns-query
• Representing DNS Messages in JSON: https://tools.ietf.org/html/rfc8427
  AFAIK this fairly young RFC is supported by DNS provided by Google and Cloudflare as application/dns-json:
  • https://developers.google.com/speed/public-dns/docs/dns-over-https
  • https://developers.cloudflare.com/1.1.1.1/dns-over-https/json-format/

If I had to pick which one use in our low level libraries, I am leaning towards binary one.
It not only gives us smaller payload sizes but also more servers support it.

[momack2]

@hugomrdias - is there a spec for the js client implementation? the go-ipfs team wants to evaluate whether we can add a go client matching that interface in time for IPFS Camp

cc @Stebalien

[momack2]

Is there a status update on this? I see the Q3 OKR "IPNS over DNS production ready" has a grade of 0.7 - does that mean there is a finalized/implemented spec?

[daviddias]

I'm also interested.

[bmann]

Great to meet you @hugomrdias. @expede and @dholms are going to take a look at this and help with the spec / give our opinion.