Dynu module for Caddy

This package contains a DNS provider module for Caddy. It can be used to manage DNS records with Dynu.

Caddy module name

dns.providers.dynu

Caddyfile definition

dynu [<api_token>] {
    api_token <api_token>
    own_domain <own_domain>
}

• api_token may be specified as an argument to the dynu directive, or in the body.
• own_domain should be set to the root domain returned from /dns/getroot/{hostname} of the Dynu API. For example, if you have a subdomain my.dynu.com, this should be set to my.dynu.com so that the correct hostname is used to update Dynu. This is needed as the zone used by Caddy DNS challenge is different from the subdomain provided by Dynu.

Config examples

To use this module for the ACME DNS challenge, configure the ACME issuer in your Caddy JSON like so:

{
	"module": "acme",
	"challenges": {
		"dns": {
			"provider": {
				"name": "dynu",
				"api_token": "YOUR_DYNU_API_TOKEN",
				"own_domain": "YOUR_OWN_DYNU_DOMAIN"
			}
		}
	}
}

or with the Caddyfile:

tls {
	dns dynu {env.DYNU_API_TOKEN} {
		own_domain {env.OWN_DYNU_DOMAIN}
	}
}

You can replace {env.DYNU_API_TOKEN} with the actual auth token if you prefer to put it directly in your config instead of an environment variable.

Authenticating

See the associated README in the libdns package for important information about credentials. Your API token can be found when logged in at https://www.dynu.com/ControlPanel/APICredentials.