volker.raschek
/
dyndns-client
1
0
Fork 0
Code Issues Pull Requests 2 Projects Releases Wiki Activity
Simple dnyndns-client based on nsupdate
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
58 Commits
3 Branches
0 Tags
168 KiB
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Go to file
CSRBot 402e35629a
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is passing Details
chore(deps): update dependency docker.io/golangci/golangci-lint to v1.51.1 		2 months ago
pkg fix: add nosec flags 1 year ago
systemd fix: remove systemd service unit for container image 1 year ago
.dockerignore Initial Commit 2 years ago
.drone.yml chore(deps): update dependency docker.io/golangci/golangci-lint to v1.51.1 2 months ago
.editorconfig Initial Commit 2 years ago
.gitattributes Initial Commit 2 years ago
.gitignore Initial Commit 2 years ago
.golangci.yml fix(ci): renovate, golang-ci lint 1 year ago
LICENSE Initial Commit 2 years ago
Makefile fix(Makefile): remove obsolete bin steps 1 year ago
README.md doc(README): drone badge 1 year ago
go.mod chore(deps): update module github.com/sirupsen/logrus to v1.9.0 9 months ago
go.sum chore(deps): update module github.com/sirupsen/logrus to v1.9.0 9 months ago
main.go style: golangci lint 1 year ago
renovate.json fix(ci): renovate, golang-ci lint 1 year ago

README.md

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=="
    }
  }
}