DomainDnsRecordRequest
Type of the record. NS and PTR records cannot be created, as in the control panel
Possible values: [A, AAAA, CNAME, MX, SRV, TXT, SPF, CAA, TLSA]
Name of the record relative to the zone, @ for the domain itself; for SRV and TLSA records, without the service and the protocol
Service of SRV records (e.g. _sip) and port of TLSA records
Protocol of SRV and TLSA records: _tcp, _udp or _tls
Value of the record: the IPv4 address for A, the IPv6 address for AAAA, the target hostname for CNAME, MX, NS, PTR and SRV, the text for TXT and SPF, the value of the tag for CAA, the certificate association data for TLSA
Port of the service, required for SRV records
Weight of SRV records
Priority of MX and SRV records
Ignored: a new record has the TTL of the zone with the standard and external nameservers, and the automatic TTL with Cloudflare, which PATCH /api/v3/domains/{domain_id}/dns/records/{record_id} can change
Whether the traffic of the record goes through the Cloudflare proxy; only with the Cloudflare nameservers
caa_data object
Use this for CAA type record only
Flags of the CAA record: only 0 is accepted
Tag of the CAA record, for example issue or issuewild; its value goes in destination
Whether to add the parameter cansignhttpexchanges=yes to the value of the tag
tlsa_data object
Use this for TLSA type record only
Certificate usage: 0 (PKIX-TA), 1 (PKIX-EE), 2 (DANE-TA) or 3 (DANE-EE)
Selector: 0 for the full certificate, 1 for its public key (SubjectPublicKeyInfo)
Matching type: 0 for the data without hashing, 1 for SHA-256, 2 for SHA-512
{
"type": "A",
"host": "string",
"service": "string",
"protocol": "string",
"destination": "string",
"port": "string",
"weight": "string",
"priority": "string",
"ttl": 0,
"proxied": true,
"caa_data": {
"flag": 0,
"tag_value": "string",
"can_sign_http_exchanges": true
},
"tlsa_data": {
"usage": "string",
"selector": "string",
"matching_type": "string"
}
}