Manage DNS records in Micetro.
In DNS it is very common to have multiple entries with the same name, as the example below shows.
mail01.example.net. 7200 IN A 192.0.2.25 mail01.example.net. 7200 IN A 192.0.2.143 mail01.example.net. 7200 IN AAAA 2001:db8::25 mail01.example.net. 7200 IN AAAA 2001:db8::587
To enable multiple records with the same name in the Ansible modules, there is no possibility to change a record, the only way is to add the new record with the updated data and remove the old one after that.
The aging timestamp of dynamic records in AD integrated zones. Hours since January 1, 1601, UTC. Providing a non-zero value creates a dynamic record.
Comment string for the record. Note that only records in static DNS zones can have a comment string
(required) The data that is added to the DNS record. The record data is a space-separated list, when the resource type is one of:
"100 10 U E2U+sip !^.*$!sip:email@example.com! ."
(required) The DNS zone where the action should take place.
True if the record is enabled. If the record is disabled the value is false
(required) The name of the DNS record. Can either be partially or fully qualified.
(required) Definition of the Micetro API provider.
Resource Record Type for this DNS record. Default is
The state of the properties. (
The Time-To-Live of the DNS record.
- name: Set DNS record in zone for a defined name mm_dnsrecord: state: present name: reynholm data: 172.16.17.2 rrtype: A dnszone: example.net. provider: mmurl: http://micetro.example.net user: apiuser password: apipasswd delegate_to: localhost
- name: Set PTR record in zone for a defined name mm_dnsrecord: state: present name: "184.108.40.206.in-addr.arpa." data: reynholm.example.net. rrtype: PTR dnszone: "17.16.172.in-addr.arpa." provider: mmurl: http://micetro.example.net user: apiuser password: apipasswd delegate_to: localhost