aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Frazee <pfrazee@gmail.com>2018-05-07 14:04:34 -0500
committerPaul Frazee <pfrazee@gmail.com>2018-05-07 14:04:34 -0500
commite391a04d9a96ddaf3e5a6fdb894aff64a7f6e946 (patch)
treeb2e4e27063de9b6dbf0b49c40ea54497883acf9e
parentaf0fc11c5e0487da95e4428e87428fdaba66cb6a (diff)
downloaddat-deps-e391a04d9a96ddaf3e5a6fdb894aff64a7f6e946.zip
dat-deps-e391a04d9a96ddaf3e5a6fdb894aff64a7f6e946.tar.gz
Lowercase the keyname in the DNS TXT record
-rw-r--r--proposals/0000-dns.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/proposals/0000-dns.md b/proposals/0000-dns.md
index 2e0b6b7..e6b2f8e 100644
--- a/proposals/0000-dns.md
+++ b/proposals/0000-dns.md
@@ -62,7 +62,7 @@ Users have multiple options for creating a domain-name mapping.
The first option is to set a DNS TXT record at the domain which maps to a "key"-addressed Dat URL. The client will lookup this TXT record first and load the resulting Dat. That record should fit the following schema:
```
-DATKEY={key}
+datkey={key}
```
## .well-known/dat
@@ -97,7 +97,7 @@ Resolution of a Dat at `dat://{name}` should follow this process:
The DNS TXT record must match this schema:
```
-'DATKEY=' [0-9a-f]{64}
+'datkey=' [0-9a-f]{64}
```
The `/.well-known/dat` file must match this schema: