dnscontrol/docs/_providers/digitalocean.md
Tom Limoncelli 8dea9edc34
Re-engineer TXT records for simplicity and better compliance (#1063)
TXT records are now handled different.

1. The raw input from dnsconfig.js is passed all the way to the provider. The provider can determine if it can or can't handle such records (auditrecords.go) and processes them internally as such.
2. The CanUseTXTMulti capability is no longer needed.

* DSPs now register a table of functions
* Use audits for txt record variations
* unit tests pass. integration fails.
* fix deepcopy problem
* rename to AuditRecordSupport
* Reduce use of TXTMulti
* Remove CanUseTXTMulti
* fix Test Skip
* fix DO
* fix vultr
* fix NDC
* msdns fixes
* Fix powerdns and cloudflare
* HEDNS: Fix usage of target field to resolve TXT handling (#1067)
* Fix HEXONET

Co-authored-by: Robert Blenkinsopp <robert@blenkinsopp.net>
Co-authored-by: Jakob Ackermann <das7pad@outlook.com>
2021-03-07 13:19:22 -05:00

1.1 KiB

name title layout jsId
DigitalOcean DigitalOcean Provider default DIGITALOCEAN

DigitalOcean Provider

Configuration

In your credentials file, you must provide your DigitalOcean OAuth Token

{% highlight json %} { "digitalocean": { "token": "your-digitalocean-ouath-token" } } {% endhighlight %}

Metadata

This provider does not recognize any special metadata fields unique to DigitalOcean.

Usage

Example Javascript:

{% highlight js %} var REG_NONE = NewRegistrar('none', 'NONE') var DIGITALOCEAN = NewDnsProvider("digitalocean", "DIGITALOCEAN");

D("example.tld", REG_NONE, DnsProvider(DIGITALOCEAN), A("test","1.2.3.4") ); {%endhighlight%}

Activation

Create OAuth Token

Limitations

  • Digitalocean DNS doesn't support ; value with CAA-records (DigitalOcean documentation)
  • While Digitalocean DNS supports TXT records with multiple strings, their length is limited by the max API request of 512 octets.