> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/configure/administration/domain-management/a-record.md).

# A record

The A record is a solution for tracking purposes using 1st party cookies.\
You need to combine A record with the [CAID on-premise cookie](/configure/administration/domain-management/cookie-caid.md) to get the most out of it.

## What is a `A record?`

A record (A for Address) is a DNS record type. It is a match between a domain and an IP address. It points the hostname to the IP address.

cs.example.com ⇒ IP Address : 36.283.49.384

## How the A record creation process works

Since there is a link between the domain and the IP address, we need to have control over it. Otherwise, it would be very complicated for maintenance: we will have to ask customers to change their configuration each time we want to upgrade the platform.

We therefore ask customers to delegate part of their DNS to us. This means that we will be able to configure the corresponding IP address for the delegated domain.

The process is quite simple, on Administration / Domain Management interface, click on 'Add subdomain' to add a domain name that will be delegated.\
Select A record and select how to provide the certificate:

* Use Let's Encrypt certificate: with this method, the certificate will be automatically generated. Follow the steps on the interface, no action is required on your side.
* Use your own certificate: this will require to provide the following elements:

  \- The SSL certificate(s) linked to the subdomain(s) entered above\
  \- The key of the certificate\
  \- The chain of the certificate\
  If you need assistance, please contact the Commanders Act support team.

![](/files/Q6KwwXjv84dx7caox2XD)

## A record setup with Let's encrypt

Customers' DNS should be configured with A record information (ask your IT department).

Click on "Validate configuration" and this will test the DNS configuration.

![](/files/0gJ1UCKAXJzjcK3kLGpX)

Click then on "Generate certificates"

![](/files/svriMV8a85jHs80J7MxJ)

Click on "Test configuration" and the setup will be done.

![](/files/kI63UOm07IixXmYoGSra)

## A record setup with your own certificate

Customers' DNS should be configured with A record information (ask your IT department).

Provide the requested information:\
\- The SSL certificate(s) linked to the subdomain(s) entered above\
\- The key of the certificate\
\- The chain of the certificate\
If you need assistance, please contact the Commanders Act support team.

![](/files/U01pEuxjDYiNFc8fO2cg)

Then click on "Validate configuration" and this will test the DNS configuration.

![](/files/BnfNXuNjxz6B6RL8bvmY)

Test the configuration and the setup will be done.

## Activate the domain

Click on "Containers Integration", this will allow the domain to be included in the container configuration.

<figure><img src="/files/KchFSmwdbnYm2JL41THD" alt=""><figcaption></figcaption></figure>

All Commanders Act tags will switch to first party collection.

This action will affect Consent, Deduplication, Campaign, Segment, Server Side

{% hint style="warning" %}
At this point, **WebContainers and Privacy banners** should be **regenerated and deployed.**
{% endhint %}

### What happens when I have 2 or more domains?

It prioritizes the domain of the website where the container is loaded. If no domain matches the domain of the website, the 1st in the list is used.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.commandersact.com/configure/administration/domain-management/a-record.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
