Skip to main content

AAAA records

AAAA records map domain names to IPv6 addresses. Use them to direct a name, such as www.example.com, to the address of the server hosting a service.

What an AAAA record is

An AAAA record associates a DNS name with an IPv6 address. For example, an AAAA record for www.example.com could point to 2001:db8::10.

You can configure AAAA records for the zone apex, such as example.com, or names within the zone, such as www.example.com and api.example.com.

Use an A record for an IPv4 address. An AAAA record’s destination must be an IPv6 address, rather than a hostname or URL.

A hostname can have both A and AAAA records when the service supports IPv4 and IPv6. Configure and maintain each record type separately.

Before publishing an AAAA record, verify that the destination service is reachable over IPv6. Adding the record does not enable IPv6 connectivity on the destination server.

For secondary zones, make record changes at the primary DNS provider. See Secondary DNS zones for details.

Explore AAAA records on the Records page

To view AAAA records, go to DNS > Zones, select Primary zones, open the zone, and select the Records tab.

In Grouped view, expand AAAA (Address - IPv6).

The table displays the following information:

Column

Description

Record name

The complete DNS name, including the zone name

IPv6 address

The destination IPv6 address or addresses

Policy

The response-selection policy associated with the record

TTL

How long the record can be cached, in seconds

Use Search to locate a record or switch to Table view to review records in a table. The reorder control lets you adjust which record-type groups are displayed and their order.

Each row provides an actions menu for editing or deleting the record. Select row checkboxes to perform bulk deletion.

Create an AAAA record

To create an AAAA record, open the zone’s Records tab:

  1. Select Add record, either at the top of the page or beside AAAA (Address - IPv6).

  2. Set Record type to AAAA (Address - IPv6).

  3. Enter the Name, or use @ for the zone apex.

  4. Enter the TTL in seconds.

  5. Leave Configure reverse PTR selected to create a corresponding PTR record, or clear it to skip reverse record creation.

    See Reverse DNS for reverse zone selection and configuration.

  6. Leave Policy set to None (Default) for a standard AAAA record.

  7. Under Destination IP addresses, enter an IPv6 address.

  8. To include more addresses, select Add another. Use the remove icon beside an address to remove that entry.

  9. Select Save and close, or Save and add another to continue creating records.

    If a duplicate is found when you save, a banner directs you to edit the existing record. Update that entry instead of creating another.

The form contains these fields:

Field

Description

Record type

The DNS record type; select AAAA (Address - IPv6)

Name

The name within the zone, or @ for the zone apex

TTL

The cache duration, in seconds

Policy

Controls how DNS responses are selected

Destination IP addresses

One or more IPv6 addresses associated with the name

The zone name appears beneath Name. For a zone named example.com, these entries produce the following names:

Name entered

Resulting record name

@

example.com

www

www.example.com

api

api.example.com

You can also add records through Import records. See Import DNS records for supported formats and validation behavior.

Update an AAAA record

  1. Locate the record on the Records tab.

  2. Open its actions menu and select Edit.

    The Record type and Name fields are read-only in the edit form.

  3. Update the TTL, Policy, or Destination IP addresses.

  4. Select Update.

To remove one destination address while retaining the other addresses, edit the record and remove the relevant address entry.

Delete an AAAA record

To delete an entire AAAA record entry, open its actions menu, select Delete, and confirm the deletion.

To delete multiple entries from the Records page

  1. Select the checkboxes beside the records.

  2. Select Delete in the selection toolbar.

  3. Review the names listed in the confirmation dialog.

  4. Select Delete.

Deletion cannot be undone. Deleting an entry removes its configured addresses, although previously cached answers may remain available until their TTL expires.

Compressed and expanded IPv6 addresses

IPv6 addresses use hexadecimal digits arranged in groups separated by colons. Expanded notation contains eight groups of four digits.

Compressed notation shortens an address by omitting leading zeros within groups and replacing a consecutive sequence of all-zero groups with ::. The :: abbreviation can appear only once in an address.

These examples represent the same IPv6 address:

Format

Example

Expanded

2001:0db8:0000:0000:0000:0000:0000:0010

Compressed

2001:db8::10

Select Expand IPv6 address beneath an address field to display its expanded notation. Select Compress IPv6 address to display the shorter notation.

Changing the notation does not change the destination address.

Enter an individual IPv6 address in each destination field. Do not include a URL scheme, port number, or network prefix such as /64.

Multiple IPv6 addresses and response policies

You can associate multiple IPv6 addresses with the same AAAA record name. DigiCert®​​ DNS displays these addresses together in one row on the Records page.

To add addresses to an existing AAAA record, edit that record and select Add another. Adding multiple addresses does not, by itself, configure health monitoring or automatic failover.

For a standard AAAA record, select None (Default). This uses the configured record without applying a response selection policy.

For availability-based responses, see Simple failover. For region-specific responses, see Regional views. Those articles explain the additional configuration required.

TTL and record changes

The TTL, or time to live, specifies how long a DNS record can be cached before it expires. Enter this value in seconds.

For example, a TTL of 300 represents five minutes.

After you update an address, resolvers may continue returning a previously cached value until its TTL expires. Changing the TTL does not shorten the lifetime of copies already cached using the previous value.

When planning an address change, consider lowering the TTL in advance and allowing the previous TTL to expire before changing the destination.