mirror of
https://github.com/StackExchange/dnscontrol.git
synced 2025-12-09 13:46:07 +08:00
[docs] Refresh digital ocean provider docs (#3860)
## Done - [docs] Refresh digital ocean provider docs by clarifying which record types are supported, linking to the digital ocean docs, and calling out other relevant internal docs. - spelling correction - update docs for chicks-net as maintainer for digital ocean ## Meta (Automated in `.just/gh-process.just`.)
This commit is contained in:
parent
986bc4c5f4
commit
db27a1e557
2 changed files with 30 additions and 2 deletions
|
|
@ -16,10 +16,14 @@ Example:
|
|||
```
|
||||
{% endcode %}
|
||||
|
||||
The [creds.json](../commands/creds-json.md#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.
|
||||
|
||||
## Limitations
|
||||
|
||||
- Digitalocean DNS doesn't support `;` value with CAA-records ([DigitalOcean documentation](https://www.digitalocean.com/docs/networking/dns/how-to/create-caa-records/))
|
||||
|
|
|
|||
|
|
@ -407,7 +407,7 @@ Providers in this category and their maintainers are:
|
|||
|[`CNR`](cnr.md)|@KaiSchwarz-cnic|
|
||||
|[`CSCGLOBAL`](cscglobal.md)|@Air-New-Zealand|
|
||||
|[`DESEC`](desec.md)|@D3luxee|
|
||||
|[`DIGITALOCEAN`](digitalocean.md)|@Deraen|
|
||||
|[`DIGITALOCEAN`](digitalocean.md)|@chicks-net|
|
||||
|[`DNSIMPLE`](dnsimple.md)|@onlyhavecans|
|
||||
|[`DNSMADEEASY`](dnsmadeeasy.md)|@vojtad|
|
||||
|[`DNSOVERHTTPS`](dnsoverhttps.md)|@mikenz|
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue