From 63f3f539d8f2c310411f409a123b76486ae3aca2 Mon Sep 17 00:00:00 2001 From: Rob Brackett Date: Thu, 23 Aug 2018 14:22:16 -0700 Subject: [PATCH] Fix grammar, heading level, and links for DNSLink License: MIT Signed-off-by: Rob Brackett --- content/guides/concepts/dnslink.md | 32 +++++++++++++----------------- 1 file changed, 14 insertions(+), 18 deletions(-) diff --git a/content/guides/concepts/dnslink.md b/content/guides/concepts/dnslink.md index 0b0139f..e968e3e 100644 --- a/content/guides/concepts/dnslink.md +++ b/content/guides/concepts/dnslink.md @@ -5,11 +5,12 @@ menu: parent: concepts --- -DNSLink uses DNS TXT records to map a domain name (like `ipfs.io`) to an IPFS -address. Because you can edit your DNS records, you can use them to always -point to the latest version of an object in IPFS (remember that an IPFS -object’s address changes if you modify the object). Because DNSLink uses DNS -records, the names it produces are also usually easy to type and read. +DNSLink uses [DNS TXT](https://en.wikipedia.org/wiki/TXT_record) records to map +a domain name (like `ipfs.io`) to an IPFS address. Because you can edit your +DNS records, you can use them to always point to the latest version of an +object in IPFS (remember that an IPFS object’s address changes if you modify +the object). Because DNSLink uses DNS records, the names it produces are also +usually easy to type and read. A DNSLink address looks like an [IPNS](/guides/concepts/ipns) address, but it uses a domain name in place of a hashed public key: @@ -24,16 +25,15 @@ Just like normal IPFS addresses, they can include links to other files: /ipns/ipfs.io/media/ ``` - When an IPFS client or node attempts to resolve that address, it looks for a `TXT` record for `ipfs.io` with content like: ``` dnslink=/ipfs/ ``` -For example, if you look up `ipfs.io`’s DNS records, you’ll see its DNSLink entry. +For example, if you look up `ipfs.io`’s DNS records, you’ll see its DNSLink entry: -``` +```sh $ dig +noall +answer TXT ipfs.io ipfs.io. 59 IN TXT "dnslink=/ipfs/QmYNQJoKGNHTpPxCBPh9KkDpaExgd2duMa3aF6ytMpHdao" ``` @@ -50,27 +50,23 @@ Will get you this block: /ipfs/QmYNQJoKGNHTpPxCBPh9KkDpaExgd2duMa3aF6ytMpHdao/media/ ``` -### Publish via Subdomain -It is possible to publish DNSLink using a special subdomain named `_dnslink`. +## Publishing via a Subdomain -This is useful when you want to improve security of automated setup or -delegate control over DNSLink to a third-party without giving full control over -the original DNS zone. +You can also publish DNSLink records using a special subdomain named `_dnslink`. This is useful when you want to improve the security of an automated setup or delegate control over your DNSLink records to a third-party without giving away full control over the original DNS zone. -Example: `docs.ipfs.io` may not not have a TXT record, but the page still loads -because TXT record exists for `_dnslink.docs.ipfs.io`: +For example, [`docs.ipfs.io`](https://docs.ipfs.io) does not have a TXT record, but the page still loads +because a TXT record exists for `_dnslink.docs.ipfs.io`: -``` +```sh $ dig +noall +answer TXT _dnslink.docs.ipfs.io _dnslink.docs.ipfs.io. 34 IN TXT "dnslink=/ipfs/QmeveuwF5wWBSgUXLG6p1oxF3GKkgjEnhA6AAwHUoVsx6E" ``` - -