Hacker News Reader

Comment by _prometheus | Hacker News Reader

Yes. (IPFS author here)

1. Add a TXT record to DNS <domain> with:

   dnslink="/ipns/QmWGb7PZmLb1TwsMkE1b8jVK4LGceMYMsWaSmviSucWPGG"

2. should be able to use https://ipfs.io/ipns/<domain>

See it in action here: https://ipfs.io/ipns/ipfs.io

WARNING: IPNS is still under dev. it's not robust yet, convergence may not be perfect.

View on HN

Also - if I remember correctly - if you visit ipfs.io with the Host header set to foo.com, it will return /ipns/foo.com.

Yes exactly, the IPFS daemon running there looks at the Host: header and uses it to build an `/ipns/<the-header>` path which it will resolve and respond accordingly.

Is there any place I can track IPNS completeness? I've seen issues / PRs / commits related to this, but just wondering if I can find a single-page/issue tracker.

Just made an issue for this after seeing your comment: https://github.com/ipfs/go-ipfs/issues/1716

There should be some progress on ipns pretty soon, i'm working on a 'phase one' fix that improves upon the current situation, and will be replaced later by our final implementation once the specification and requirements for it are complete.

How is "ownership" over a domain resolved?

Just classic DNS -- you set a TXT record on that domain, and IPFS uses standard DNS resolution to get the value of it.

Reply on news.ycombinator.com