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.
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.
While IPNS is indeed a way of assigning and reassigning names, it is not very user friendly, as it exposes long hash values as names, which are notoriously hard to remember. These work for URLs, but not for many kinds of offline transmission. Thus, IPFS increases the user-friendliness of IPNS with the following techniques.
[1] https://github.com/ipfs/papers/raw/master/ipfs-cap2pfs/ipfs-...
For example, the ipfs.io site is hosted on ipfs/ipns, and available through the gateway at https://gateway.ipfs.io/ipns/ipfs.io/