From e104767f136209841bb10ca0de438a739da311b2 Mon Sep 17 00:00:00 2001 From: Thomas Preisner Date: Sat, 16 Oct 2021 22:30:00 +0200 Subject: [PATCH 1/3] drone-ci: also generate sha512 checksum for releases --- .drone.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.drone.yml b/.drone.yml index bf92a03..77d6da8 100644 --- a/.drone.yml +++ b/.drone.yml @@ -20,5 +20,6 @@ steps: - dyndns-server checksum: - sha256 + - sha512 when: event: tag From c21c47892e6220207e269cbeda8b74bc3057bce8 Mon Sep 17 00:00:00 2001 From: Thomas Preisner Date: Sat, 20 Nov 2021 00:42:04 +0100 Subject: [PATCH 2/3] add README.md --- README.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..3326e99 --- /dev/null +++ b/README.md @@ -0,0 +1,24 @@ +dyndns-server +============= + +`dyndns-server` is a simple self-hosted dynamic DNS API service which can be used +together with e.g. AVM FritzBox's DynDNS functionality or +[ddclient](https://github.com/ddclient/ddclient). It implements a subset of the +API described by +[Google Domains](https://support.google.com/domains/answer/6147083?hl=en#zippy=%2Cuse-the-api-to-update-your-dynamic-dns-recordhttps://support.google.com/domains/answer/6147083?hl=en#zippy=%2Cuse-the-api-to-update-your-dynamic-dns-record) +and forwards DNS Updates to an authoritive DNS server as per +[RFC2136](https://datatracker.ietf.org/doc/html/rfc2136). + +Requirements +------------- + - `go` for building the `dyndns-server` binary + - an authoritive DNS server responsible for the records to be dynamically + updated which is capable of RFC2136 (e.g. knot, bind) + - `knsupdate` needs to be installed for sending DNS update requests + +Configuration +------------- +`dyndns-server` will look for a file named `config.toml` inside the current +working directory unless a different config path has been supplied via `-config +`. For details regarding the configuration file format, +please consult `config.example.toml`. From 7e4452347fa2b492700fa37d404e51d7e8aea008 Mon Sep 17 00:00:00 2001 From: Thomas Preisner Date: Sat, 20 Nov 2021 00:46:24 +0100 Subject: [PATCH 3/3] README.md: add reverse proxy as optional requirement --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index 3326e99..3170985 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,9 @@ Requirements - an authoritive DNS server responsible for the records to be dynamically updated which is capable of RFC2136 (e.g. knot, bind) - `knsupdate` needs to be installed for sending DNS update requests + - a reverse-proxy for https (e.g. nginx), this is optional and `dyndns-server` + can also directly operate at port 80 which is discouraged as otherwise + secrets will be transmitted unencrypted Configuration -------------