mirror of
https://github.com/StackExchange/dnscontrol.git
synced 2025-12-09 21:55:57 +08:00
Closes https://github.com/StackExchange/dnscontrol/issues/3787
This PR is adding a `HETZNER_V2` provider for the "new" Hetzner DNS API.
Testing:
- The integration tests are passing.
- Manual testing:
- `preview` (see diff for existing zone)
- `preview --populate-on-preview` (see full diff for newly created zone)
- `push` (see full diff; no diff after push)
- `push` (see full diff; no diff after push to newly created zone --
i.e. single pass and done)
```js
var REG_NONE = NewRegistrar('none')
var DSP = NewDnsProvider('HETZNER_V2')
D('testing-2025-11-14-7.dev', REG_NONE, DnsProvider(DSP),
A('@', '127.0.0.1')
)
```
<details>
```
# push for newly created zone
CONCURRENTLY checking for 1 zone(s)
SERIALLY checking for 0 zone(s)
Waiting for concurrent checking(s) to complete...DONE
******************** Domain: testing-2025-11-14-7.dev
1 correction (HETZNER_V2)
#1: Ensuring zone "testing-2025-11-14-7.dev" exists in "HETZNER_V2"
SUCCESS!
CONCURRENTLY gathering records of 1 zone(s)
SERIALLY gathering records of 0 zone(s)
Waiting for concurrent gathering(s) to complete...DONE
******************** Domain: testing-2025-11-14-7.dev
4 corrections (HETZNER_V2)
#1: ± MODIFY-TTL testing-2025-11-14-7.dev NS helium.ns.hetzner.de. ttl=(3600->300)
± MODIFY-TTL testing-2025-11-14-7.dev NS hydrogen.ns.hetzner.com. ttl=(3600->300)
± MODIFY-TTL testing-2025-11-14-7.dev NS oxygen.ns.hetzner.com. ttl=(3600->300)
SUCCESS!
#2: + CREATE testing-2025-11-14-7.dev A 127.0.0.1 ttl=300
SUCCESS!
Done. 5 corrections.
```
</details>
Feedback for @jooola and @LKaemmerling:
- The SDK was very useful in getting 80% there! Nice! 🎉
- Footgun:
- The `result` values are not "up-to-date" after waiting for an
`Action`, e.g. `Zone.AuthoritativeNameservers.Assigned` is not set when
`Client.Zone.Create()` returns and the following "wait" will not update
it.
- Taking a step back here: Waiting for an `Action` with a separate SDK
call does not seem very natural to me. Does the SDK-user need to know
that you are processing operations asynchronous? (Which seems like an
implementation detail to me, something that the SDK could abstrct over.)
Can `Client.Zone.Create()` return the final `Zone` instead of the
intermediate result?
- Features missing compared to the DNS Console, in priority order:
- It is no longer possible to remove your provided name servers from the
root/apex. Use-case: dual-home/multi-home zone with fewer than three
servers from Hetzner. I'm operating one of these and cannot migrate over
until this is fixed.
- Performance regression due to lack of bulk create/modify. E.g. [one of
the test
suites](a71b89e5a2/integrationTest/integration_test.go (L619))
spends about 4.5 minutes on making creating 100 record-sets and then
another 4 minutes for deleting them in sequence again. With your async
API, these are `create 2*100 + delete 2*100 = 400` API calls.
Previously, these were `create 1 + delete 100 = 101` API calls. Are you
planning on adding batch processing again?
- Usability nits
- Compared to other record-set based APIs, upserts for record-sets are
missing. This applies to records of a record-set and the ttl of the
record-set (see separate SDK calls for the cases `diff2.CREATE` vs
`diff2.CHANGE` and two calls in `diff2.CHANGE` for updating the TTL vs
records).
- Some SDK methods return an `Action` (e.g. `Zone.ChangeRRSetTTL()`),
others wrap the `Action` in a struct (`Client.Zone.CreateRRSet()`) --
even when the struct has a single field (`ZoneRRSetDeleteResult`).
---------
Co-authored-by: "Jonas L." <jooola@users.noreply.github.com>
Co-authored-by: "Lukas Kämmerling" <LKaemmerling@users.noreply.github.com>
Co-authored-by: Tom Limoncelli <6293917+tlimoncelli@users.noreply.github.com>
10 KiB
10 KiB
Table of contents
Getting Started
Language Reference
- JavaScript DSL
- Top Level Functions
- Domain Modifiers
- A
- AAAA
- ALIAS
- AUTODNSSEC_OFF
- AUTODNSSEC_ON
- CAA
- CAA_BUILDER
- CNAME
- DHCID
- DNAME
- DNSKEY
- DISABLE_IGNORE_SAFETY_CHECK
- DKIM_BUILDER
- DMARC_BUILDER
- DS
- DefaultTTL
- DnsProvider
- FRAME
- HTTPS
- IGNORE
- IGNORE_NAME
- IGNORE_TARGET
- IMPORT_TRANSFORM
- IMPORT_TRANSFORM_STRIP
- INCLUDE
- LOC
- LOC_BUILDER_DD
- LOC_BUILDER_DMM_STR
- LOC_BUILDER_DMS_STR
- LOC_BUILDER_STR
- M365_BUILDER
- MX
- NAMESERVER
- NAMESERVER_TTL
- NAPTR
- NO_PURGE
- NS
- OPENPGPKEY
- PTR
- PURGE
- SMIMEA
- SOA
- SPF_BUILDER
- SRV
- SSHFP
- SVCB
- TLSA
- TXT
- URL
- URL301
- Service Provider specific
- AdGuard Home
- Akamai Edge Dns
- Amazon Route 53
- Azure DNS
- Cloudflare DNS
- ClouDNS
- PowerDNS
- Record Modifiers
- TTL
- Service Provider specific
- Amazon Route 53
- Why CNAME/MX/NS targets require a "dot"
Provider
- Supported providers
- AdGuard Home
- Akamai Edge DNS
- Amazon Route 53
- AutoDNS
- AXFR+DDNS
- Azure DNS
- Azure Private DNS
- BIND
- Bunny DNS
- CentralNic Reseller (CNR) - formerly RRPProxy
- Cloudflare
- ClouDNS
- CSC Global
- deSEC
- DigitalOcean
- DNS Made Easy
- DNSimple
- DNS-over-HTTPS
- DOMAINNAMESHOP
- Dynadot
- easyname
- Exoscale
- Fortigate
- Gandi_v5
- Gcore
- Google Cloud DNS
- Hetzner DNS API
- Hetzner DNS Console (legacy)
- HEXONET
- hosting.de
- Huawei Cloud DNS
- Hurricane Electric DNS
- Internet.bs
- INWX
- Joker
- Linode
- Loopia
- LuaDNS
- Mythic Beasts
- Namecheap
- Name.com
- Netcup
- Netlify
- NS1
- OpenSRS
- Oracle Cloud
- OVH
- Packetframe
- Porkbun
- PowerDNS
- Realtime Register
- RWTH DNS-Admin
- Sakura Cloud
- SoftLayer DNS
- TransIP
- Vultr
Commands
Advanced features
- Concurrency Verified
- CI/CD example for GitLab
- CLI variables
- Nameservers and Delegations
- Notifications
- Useful code tricks
- JSON Reports
- Dual Host
Developer info
- Code Style Guide
- Documentation Style Guide
- DNSControl is an opinionated system
- Writing new DNS providers
- Creating new DNS Resource Types (rtypes)
- Integration Tests
- Test a branch
- Unit Testing DNS Data
- Bug Triage Process
- Bring-Your-Own-Secrets for automated testing
- Debugging with dlv
- ALIAS Records
- TXT record testing
- DNS records ordering
- How to add a requested provider