Simple dnyndns-client based on nsupdate
Go to file
CSRBot af3e11b944
All checks were successful
continuous-integration/drone/pr Build is passing
continuous-integration/drone/push Build is passing
chore(deps): update git.cryptic.systems/volker.raschek/markdownlint docker tag to v0.41.0
2024-05-27 13:16:44 +00:00
pkg
systemd
.dockerignore
.drone.yml chore(deps): update git.cryptic.systems/volker.raschek/markdownlint docker tag to v0.41.0 2024-05-27 13:16:44 +00:00
.editorconfig
.gitattributes
.gitignore
.golangci.yml
go.mod fix: upgrade direct dependencies 2023-07-08 19:17:30 +02:00
go.sum fix: upgrade direct dependencies 2023-07-08 19:17:30 +02:00
LICENSE
main.go
Makefile
README.md doc(README): drone badge 2022-03-11 11:51:31 +01:00
renovate.json fix(renovate): remove automerge options 2024-01-21 15:02:07 +01:00

dyndns-client

Build Status

dyndns-client is a Daemon to listen on interface notifications produced by the linux kernel of a client machine to update one or more DNS zones.

Usage

To start dyndns-client just run ./dyndns-client.

Configuration

The program is compiled as standalone binary without third party libraries. If no configuration file available under /etc/dyndns-client/config.json, than will be the burned in configuration used. If also no configuration be burned into the source code, that the client returned an error.

The example below describes a configuration to update RRecords triggerd by the interface br0 for the example.com zone. To update the zone is a TSIG-Key required.

{
  "interfaces": [
    "br0"
  ],
  "zones": {
    "example.com": {
      "dns-server": "10.6.231.5",
      "name": "example.com",
      "tsig-key": "my-key"
    }
  },
  "tsig-keys": {
    "my-key": {
      "algorithm": "hmac-sha512",
      "name":      "my-key",
      "secret":    "asdasdasdasdjkhjk38hcn38haoĆ¼2390dndaskdTTWA=="
    }
  }
}