Record sets - Aptranet Developers

A record set groups one owner name and type with a TTL and one or more resource records. Routing pickers and health-check metadata apply to the set or its individual values.

Supported types

Type	Common use
A / AAAA	IPv4 or IPv6 address
CNAME	Alias one name to another
MX	Mail exchange with priority
TXT	Verification, sender policy, and arbitrary text
NS	Nameserver or subdomain delegation
SRV	Service target, port, weight, and priority
CAA	Certificate authority authorization
PTR	Reverse mapping in a reverse zone
HTTPS / SVCB	Service endpoints and connection parameters
DS	Secure delegation to a DNSSEC-enabled child zone

Create an A record set

curl --request POST \
  --url "https://api.aptranet.com/cloud-dns/rrsets?zone_id=17" \
  --header "Authorization: Bearer $APTRANET_ACCESS_KEY" \
  --header "Aptranet-Secret: $APTRANET_SECRET" \
  --header "Content-Type: application/json" \
  --data '{
    "name": "www",
    "type": "A",
    "ttl": 300,
    "resource_records": [
      {"enabled": true, "content": ["192.0.2.10"]},
      {"enabled": true, "content": ["192.0.2.11"]}
    ]
  }'

The console offers common TTLs from 2 minutes through 1 day. The API accepts seconds subject to service validation.

Record content

content is an array because some DNS types contain multiple ordered fields. Enter values in the order required by the type. For example, an MX value includes priority and target, while an SRV value includes priority, weight, port, and target.

Editing safely

The update operation replaces the record set’s TTL, routing metadata, picker chain, and resource-record collection with the submitted document. Fetch the current record set, preserve fields you are not changing, and submit the complete intended state.

DNS caches can continue returning a deleted or replaced value until its previous TTL expires.