Linode
Configuration
To use this provider, add an entry to creds.json with TYPE set to LINODE along with your Linode Personal Access Token.
Example:
{
"linode": {
"TYPE": "LINODE",
"token": "your-linode-personal-access-token"
}
}Metadata
This provider does not recognize any special metadata fields unique to Linode.
Usage
An example configuration:
var REG_NONE = NewRegistrar("none");
var DSP_LINODE = NewDnsProvider("linode");
D("example.com", REG_NONE, DnsProvider(DSP_LINODE),
A("test", "1.2.3.4"),
);Activation
Caveats
Linode does not allow all TTLs, but only a specific subset of TTLs. The following TTLs are supported (source):
0 (Default: the Default TTL configured for the zone)
30 ("30s")
120 ("2m")
300 ("5m")
3600 ("1h")
7200 ("2h")
14400 ("4h")
28800 ("8h")
57600 ("16h")
86400 ("1d")
172800 ("2d")
345600 ("4d")
604800 ("1w")
1209600 ("2w")
2419200 ("4w")
The provider will automatically round up your TTL to one of these values. For example, 600 seconds would become 3600 seconds, but 300 seconds would stay 300 seconds.
Linode validates labels of SRV records more strictly than DNSControl, only permitting certain service names and protocols. Most issues will be caught at check and preview but certain errors will not be caught until DNSControl push as they rely on the API rejecting the update. Also be aware that some invalid service names are silently corrected by Linode, in which case every push will try to undo the correction. All of these caveats only affect invalid inputs.
Feature Summary
Provider Type
Official Support: β
DNS Provider: β
Registrar: β
Provider API
Concurrency Verified: β
dual host: β
create-domains: β
get-zones: β
DNSSEC
AUTODNSSEC: βDNSKEY: βDS: β
Last updated