volker.raschek
/
dyndns-client
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity
Simple dnyndns-client based on nsupdate
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
76 Commits
2 Branches
0 Tags
249 KiB
Go 90.9%
Makefile 9.1%
 
 
renovate/docker.io-library-golang-1.x
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Go to file
Markus Pesch f08252791f Merge pull request 'chore(deps): update git.cryptic.systems/volker.raschek/markdownlint docker tag to v0.37.0' (#55) from renovate/git.cryptic.systems-volker.raschek-markdownlint-0.x into master 
Reviewed-on: #55
 		1 day ago
pkg fix: add nosec flags 2 years ago
systemd fix: remove systemd service unit for container image 2 years ago
.dockerignore Initial Commit 2 years ago
.drone.yml chore(deps): update git.cryptic.systems/volker.raschek/markdownlint docker tag to v0.37.0 3 days 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 2 years ago
LICENSE Initial Commit 2 years ago
Makefile fix(Makefile): remove obsolete bin steps 2 years ago
README.md doc(README): drone badge 2 years ago
go.mod fix: upgrade direct dependencies 3 months ago
go.sum fix: upgrade direct dependencies 3 months ago
main.go style: golangci lint 2 years ago
renovate.json fix(ci): renovate, golang-ci lint 2 years 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=="
    }
  }
}