mirror of
https://github.com/StackExchange/dnscontrol.git
synced 2026-01-20 07:01:52 +08:00
ecbfa9b4a0
## Context
Filenames for providers are not consistent.
https://github.com/StackExchange/dnscontrol/issues/3584#issuecomment-3633894582
## Changes
Rename files:
```
R documentation/provider/azure_dns.md -> documentation/provider/azuredns.md
R documentation/provider/azure_private_dns.md -> documentation/provider/azureprivatedns.md
R documentation/provider/bunny_dns.md -> documentation/provider/bunnydns.md
R documentation/provider/gandi_v5.md -> documentation/provider/gandiv5.md
R documentation/provider/hetzner_v2.md -> documentation/provider/hetznerv2.md
R providers/gandiv5/gandi_v5Provider.go -> providers/gandiv5/gandiv5Provider.go
```
## Verify
- `go build` still works.
- docs generation still works for me locally.
- I see. the Azure docs in the test site for the docs again after
f5767f4
---------
Co-authored-by: Tom Limoncelli <6293917+tlimoncelli@users.noreply.github.com>
1.2 KiB
1.2 KiB
Configuration
To use this provider, add an entry to creds.json with TYPE set to HETZNER_V2
along with a Hetzner API Token.
Example:
{% code title="creds.json" %}
{
"hetzner_v2": {
"TYPE": "HETZNER_V2",
"api_token": "your-api-token"
}
}
{% endcode %}
Metadata
This provider does not recognize any special metadata fields unique to Hetzner DNS API.
Usage
An example configuration:
{% code title="dnsconfig.js" %}
var REG_NONE = NewRegistrar("none");
var DSP_HETZNER = NewDnsProvider("hetzner_v2");
D("example.com", REG_NONE, DnsProvider(DSP_HETZNER),
A("test", "1.2.3.4"),
);
{% endcode %}
Activation
Create a new API Key in the Hetzner Console.
Caveats
NS
Removing the Hetzner provided NS records at the root is not possible.
SOA
Hetzner DNS API does not allow changing the SOA record via their API. There is an alternative method using an import of a full BIND file, but this approach does not play nice with incremental changes or ignored records. At this time you cannot update SOA records via DNSControl.