-
Notifications
You must be signed in to change notification settings - Fork 471
DIGITALOCEAN: DOCS: Refresh digital ocean provider docs #3860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
d5ab886
307ce5c
9315df5
aa2bb6b
3d7219f
1ef9697
b142af2
6fee1fa
59688ba
039f227
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
|
|
@@ -16,10 +16,14 @@ Example: | |||
| ``` | ||||
| {% endcode %} | ||||
|
|
||||
| The [creds.json](/commands/creds.json#example-commands) page in the docs explains how you can generate this dynamically so you can pull the secret token from 1Password or the vault of your choosing. | ||||
|
|
||||
| ## Metadata | ||||
|
|
||||
| This provider does not recognize any special metadata fields unique to DigitalOcean. | ||||
|
|
||||
| ## Usage | ||||
|
|
||||
| An example configuration: | ||||
|
|
||||
| {% code title="dnsconfig.js" %} | ||||
|
|
@@ -34,10 +38,34 @@ D("example.com", REG_NONE, DnsProvider(DSP_DIGITALOCEAN), | |||
| {% endcode %} | ||||
|
|
||||
| ## Activation | ||||
| [Create Personal Access Token](https://cloud.digitalocean.com/account/api/tokens) | ||||
|
|
||||
| - [Create Personal Access Token](https://cloud.digitalocean.com/account/api/tokens) | ||||
| - [How to Create a Personal Access Token (documentation)](https://docs.digitalocean.com/reference/api/create-personal-access-token/) | ||||
|
|
||||
| Your access token must have access to create, read, update and delete domain records. | ||||
|
|
||||
| ## Supported record types | ||||
|
|
||||
| The [API reference](https://docs.digitalocean.com/reference/api/digitalocean/#tag/Domain-Records) states that these record types are supported: | ||||
|
|
||||
| | Name | Description | | ||||
| | ----- | ----------- | | ||||
| | A | This record type is used to map an IPv4 address to a hostname. | | ||||
| | AAAA | This record type is used to map an IPv6 address to a hostname. | | ||||
| | CAA | As specified in RFC-6844, this record type can be used to restrict which certificate authorities are permitted to issue certificates for a domain. | | ||||
| | CNAME | This record type defines an alias for your canonical hostname (the one defined by an A or AAAA record). | | ||||
| | MX | This record type is used to define the mail exchanges used for the domain. | | ||||
| | NS | This record type defines the name servers that are used for this zone. | | ||||
| | TXT | This record type is used to associate a string of text with a hostname, primarily used for verification. | | ||||
| | SRV | This record type specifies the location (hostname and port number) of servers for specific services. | | ||||
| | SOA | This record type defines administrative information about the zone. Can only have ttl changed, cannot be deleted | | ||||
|
|
||||
| ## Unsupported record types | ||||
|
|
||||
| This means that `ALIAS`, `DHCID`, `DNAME`, `DS`, `FRAME`, `HTTPS`, `LOC`, `OPENPGPKEY`, `PTR`, `SMIMEA`, `SSHFP`, `SVCB`, `TLSA`, `URL`, or `URL301` presumably **do not work** with Digital Ocean. | ||||
|
|
||||
| In 2025, the provider maintainer has confirmed that `ALIAS` and `LOC` records are rejected. The other ones that do not work are expected in this circumstance. `SPF` records are not a problem since they are turned into `TXT` record types. | ||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These rejects could/should be added to
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Absolutely agree that some of this research needs to get carried over into code. I'm planning on circling back with that soon. I'm still trying to figure out what the code-level priorities should be to have this provider following the project's best practices. 😁 |
||||
|
|
||||
| ## Limitations | ||||
|
|
||||
| - Digitalocean DNS doesn't support `;` value with CAA-records ([DigitalOcean documentation](https://www.digitalocean.com/docs/networking/dns/how-to/create-caa-records/)) | ||||
|
|
||||
This comment was marked as resolved.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for catching this. I've tried a variety of relative incantations and none seem to work so far. I feel like
../commands/creds-json#example-commandsshould work - see https://docs.dnscontrol.org/~/revisions/0Am6Ovu9k4Q2mNtPFZC6/provider/digitalocean and b142af2 for it not working.I might try a few more combinations, but I'm out of ideas.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I finally found the right combination when I found an example. I was having trouble finding an example because noone else is referring directly to the commands directory.
Is there any more that should be done for this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, that was all.