community.dns.hetzner_dns_record_sets module – Bulk synchronize DNS record sets in Hetzner DNS service
Note
This module is part of the community.dns collection (version 2.6.4).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.dns
.
To use it in a playbook, specify: community.dns.hetzner_dns_record_sets
.
New in community.dns 2.0.0
Synopsis
Bulk synchronize DNS record sets in Hetzner DNS service.
It is possible to ignore certain record sets by specifying
record_sets[].ignore=true
for that record set.The module allows to set, modify and delete multiple DNS record sets at once.
With the
prune
option, it is also possible to delete existing record sets that are not mentioned in the module parameters. With this, it is possible to synchronize the expected state of a DNS zone with the expected state.
Parameters
Parameter |
Comments |
---|---|
Determines the threshold from when on bulk operations are used. The default value 2 means that if 2 or more operations of a kind are planned, and the API supports bulk operations for this kind of operation, they will be used. Default: |
|
The token for the Hetzner API. If not provided, will be read from the environment variable |
|
If set to Choices:
|
|
The records that should be present in the zone. |
|
If set to This is useful when Choices:
|
|
The prefix of the DNS record. This is the part of Exactly one of |
|
The full DNS record to create or delete. Exactly one of |
|
The TTL to give the new record, in seconds. |
|
The type of DNS record to create or delete. Choices:
|
|
The new value when creating a DNS record. YAML lists or multiple comma-spaced values are allowed. When deleting a record all values for the record must be specified or it will not be deleted. Must be specified if |
|
Whether to treat numeric escape sequences ( The current default is Choices:
|
|
Determines how TXT entry values are converted between the API and this module’s input and output. The value The value The value The default value, Note: the conversion code assumes UTF-8 encoding for values. If you need another encoding use Choices:
|
|
Attributes
Attribute |
Support |
Description |
---|---|---|
Action group: community.dns.hetzner added in community.dns 2.4.0 |
Use |
|
Support: full |
Can run in |
|
Support: full |
Will return details on what has changed (or possibly needs changing in |
Notes
Note
For
CNAME
records, use absolute DNS names for values. Absolute DNS names end with a trailing period.
, for examplefoo.example.com.
. If you use a relative DNS name, with no trailing period, the value will be relative to the zone of theCNAME
record.
Examples
- name: Make sure some records exist and have the expected values
community.dns.hetzner_dns_record_sets:
zone: foo.com
records:
- prefix: new
type: A
ttl: 7200
value:
- 1.1.1.1
- 2.2.2.2
- prefix: new
type: AAAA
ttl: 7200
value:
- "::1"
- record: foo.com
type: TXT
value:
- test
hetzner_token: access_token
- name: Synchronize DNS zone with a fixed set of records
# If a record exists that is not mentioned here, it will be deleted
community.dns.hetzner_dns_record_sets:
zone_id: 23
purge: true
records:
- prefix: ''
type: A
value: 127.0.0.1
- prefix: ''
type: AAAA
value: "::1"
- prefix: ''
type: NS
value:
- ns-1.hoster.com
- ns-2.hoster.com
- ns-3.hoster.com
hetzner_token: access_token
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The ID of the zone. Returned: success Sample: |