diff options
author | 2020-07-27 10:15:49 +0200 | |
---|---|---|
committer | 2020-07-27 10:15:49 +0200 | |
commit | ef33425487033c6c68610ecf763b2185df4df3e5 (patch) | |
tree | 69b52554b40bd31a03f032ed0467e11f4834e148 /plugin/torrent/README.md | |
parent | 05751bdb59737221367f13413a83451e38bce355 (diff) | |
download | coredns-ef33425487033c6c68610ecf763b2185df4df3e5.tar.gz coredns-ef33425487033c6c68610ecf763b2185df4df3e5.tar.zst coredns-ef33425487033c6c68610ecf763b2185df4df3e5.zip |
Add setup func
Signed-off-by: Miek Gieben <miek@miek.nl>
Diffstat (limited to 'plugin/torrent/README.md')
-rw-r--r-- | plugin/torrent/README.md | 48 |
1 files changed, 48 insertions, 0 deletions
diff --git a/plugin/torrent/README.md b/plugin/torrent/README.md new file mode 100644 index 000000000..890bb8e3b --- /dev/null +++ b/plugin/torrent/README.md @@ -0,0 +1,48 @@ +# torrent + +## Name + +*torrent* - use BitTorrent to disseminate zone data. + +## Description + +The *torrent* plugin uses the BitTorrent protocol to disseminate zone data. Multiple peers can +connect and down- and upload the data. A couple of nodes can be `seed` only meaning they will update +the torrent when their zone data changes. Non-`seed` peers will write received data back into the +zonefile - once the torrent is fully downloaded. + +## Syntax + +The simplest syntax is for a peer wanting to receive the zone data: + +~~~ txt +torrent DBFILE +~~~ + +* **DBFILE** the zone database file to torrent. If the path is relative, the path from the + *root* plugin will be prepended to it. + +For peers seeding the torrent use this, slightly expanded, syntax + +~~~ txt +torrent DBFILE { + seed +} +~~~ + +* `seed` tells *torrent* to seed content from **DBFILE** to the peers, it will _never_ write to + **DBFILE**. When `seed` is _not_ specified **DBFILE** will be written to once the entire torrent + is downloaded. + +## Examples + +~~~ txt +example.org { + file db.example.org + torrent db.example.org +} +~~~ + +## Also See + +## Bugs |