POST - Create a AAAA record in a Zone

Purpose

This API creates AAAA records for a specified zone, enabling administrators to define domain-to-IPv6 address mappings. It supports modern networking by enabling DNS resolution for domains associated with IPv6 addresses under the selected cluster and zone.

Request URL

Method: POST

https://{appconsole_IP}:{9443}/api/dns/zone/{zone_pk}/AAAA/

Request Headers

The following headers must be included in the API request for successful authentication and data submission:

Authorization: DDI Central's OAuth implementation uses the Bearer authentication scheme. Hence, while making API calls, access_token obtained via the OAuth 2.0 Client Credentials Grant must be included in the Authorization header of API requests. This token verifies the client’s identity and ensures appropriate permissions for accessing resources.

The Authorization Header follows the format below:

headers = { "Authorization": "Bearer {bearer_tk}" }


Content-Type: Required in the header to indicate the media type of the resource being sent. It helps the server at the receiving end understand how to process the transmitted request body.

The Content-Type Header follows the format below:

headers ={ "Content-Type": "application/json" }

Path Parameters

  • zone_pk* long
    • The unique ID of the zone under which the AAAA records are being created.

Request Body

  • domain_name* string
    • The fully qualified domain name (FQDN) for which AAAA records are being created (e.g., aaaa26.hellotest109.com.).
  • domain_ttl* integer
    • Specifies how long DNS resolvers should cache the AAAA record before querying it again.
  • zone_name* string
    • The name of the DNS zone where the AAAA records will be created (e.g., hellotest109.com.).
  • ptr* boolean
    • When set to true, DDI Central will automatically create reverse PTR records for each IPv6 address listed in the AAAA record. PTRs will point to the domain_name supplied in the request. Default: false.
      •  
      Note: If the AAAA records contain these IPv6 addresses:

      85c3:9a88:0933:b20d:9a62:2e42:3965:0f7e
      a5c3:9a88:0933:b20d:9a62:2e42:3965:0f7e

      and you call the POST API with "ptr": "true", DDI Central will create the corresponding IPv6 reverse PTR entries (in ip6.arpa.) that resolve to the hostname in domain_name (for example: aaaa26.hellotest109.com.). Concretely, the PTR records created will be:

      e.7.f.0.5.6.9.3.2.4.e.2.2.6.a.9.d.0.2.b.3.3.9.0.8.8.a.9.3.c.5.8.ip6.arpa. → aaaa26.hellotest109.com.

      e.7.f.0.5.6.9.3.2.4.e.2.2.6.a.9.d.0.2.b.3.3.9.0.8.8.a.9.3.c.5.a.ip6.arpa. → aaaa26.hellotest109.com.

      Info: PTR (reverse) records are stored under the reverse ip6.arpa. zone that corresponds to the chosen network prefix.
      Example: For a /64 above, the reverse zone label would begin with the 16-nibble reverse of 85c3:9a88:0933:b20d (i.e. d.0.2.b.3.3.3.9.0.8.8.a.9.3.c.5.8.ip6.arpa.). Auto PTRs for the individual addresses will be created under that reverse zone.
    • records* array of strings
      • An array of IPv6 addresses associated with the domain name (e.g., ["85c3:9a88:0933:b20d:9a62:2e42:3965:0f7e", "a5c3:9a88:0933:b20d:9a62:2e42:3965:0f7e"]). Multiple IPv6 addresses can be associated with the domain name to provide redundancy or load balancing.
    • cluster_name* string
      • The name of the cluster where the zone resides (e.g., wincluster-zoho).

 

* - Mandatory parameter.

 

Sample Request

Copied
{
  "domain_name": "aaaa26.hellotest109.com.",
  "domain_ttl": 8640,
  "zone_name": "hellotest109.com.",
  "ptr": "false",
  "records": [
    "85c3:9a88:0933:b20d:9a62:2e42:3965:0f7e",
    "a5c3:9a88:0933:b20d:9a62:2e42:3965:0f7e"
  ],
  "cluster_name": "wincluster-zoho"
}

Sample Response

Copied
{
  "aaaa_domain_id": 10855,
  "zone_id": 5867,
  "cluster_name": "wincluster-zoho",
  "domain_name": "aaaa26.hellotest109.com.",
  "domain_ttl": 8640,
  "records": [
    "85c3:9a88:0933:b20d:9a62:2e42:3965:0f7e",
    "a5c3:9a88:0933:b20d:9a62:2e42:3965:0f7e"
  ]
}