Fork of name-dyndns using canode for external IP
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.
Kevin MacMartin 7a54e0b4e0 Use the private repo for includes 3 years ago
api Update comments and names according to go lint. 8 years ago
dyndns Use the private repo for includes 3 years ago
log Update comments and names according to go lint. 8 years ago
scripts Fix description. systemd prints out 'Starting [description' in log. 8 years ago
.gitignore Initial code commit 8 years ago
.travis.yml Update build version 7 years ago
LICENSE Initial commit 8 years ago
README.md Only update A domains, since we're mapping to an IP. 6 years ago
main.go Use the private repo for includes 3 years ago

README.md

name-dyndns Build Status GoDoc

Client that automatically updates name.com DNS records.

Getting name-dyndns

Since name-dyndns has no external dependencies, you can get it simply by:

go get github.com/mfycheng/name-dyndns

Requirements

In order to use name-dyndns, you must have an API key from name.com, which can be requested from https://www.name.com/reseller/apply.

Once you have your API key, all you must do is setup config.json. An example config.json file can be found in api/config_test.json.

Command Line Arguments

By default, running name-dyndns will run a one-time update, using ./config.json as a configuration file, and stdout as a log output. However, these can be configured. For example:

./name-dyndns -daemon=true -dev=true -log="/var/log/name-dyndns/out.log" -config="~/name_config.json"

This will run name-dyndns in daemon mode for dev configurations, outputting to /var/log/name-dyndns/out.log, using the configuration file ~/name_config.json

A detailed usage can be found by running:

./name-dyndns --help

Error Handling

Currently, there is limited testing, primarily on name-api dependant utilities. While error handling should be done gracefully, not every edge case has been tested.

Ideally, when running in daemon mode, name-dyndns tries to treat any errors arising from network as transient failures, and tries again next iteration. The idea behind this is that a single network failure shouldn't kill the daemon, which could then potentially result in having the DNS records out of sync, which would defeat the whole point of name-dyndns.