> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/getting-started/quickstart/make-tracking-first-party-set-your-dns.md).

# Make Tracking First-Party: Set Your DNS

How to set the DNS A-record for JENTIS and your website.

JENTIS is a first-party tool that becomes part of your main tool stack, just like your shop- or content management system. Therefore, you must grant it certain privileges that third parties would not have, which also indicates a higher level of data security and privacy.

That means you must create a DNS entry for a particular subdomain on your hosting. This subdomain is the main communication channel JENTIS uses. To recognize hits from the same user (via first-party cookies) and send data to the JENTIS backend server side.

A DNS A (Address) record maps a domain name to an IP address, allowing browsers and other devices to locate your server.

## **Why is an A-Record needed for JENTIS?**

Adding the DNS A-Record to your hosting settings ensures that the tracking requests made from your website are correctly routed to the JENTIS server. Essentially, it enables communication between your website and JENTIS’s server-side infrastructure.

Please access your DNS management console (usually provided by your hosting provider or domain registrar) and add the DNS settings informed in your JENTIS Account as explained below:

## Entries <a href="#dnssetup-entries" id="dnssetup-entries"></a>

In preparation for the JENTIS implementation, you will find specific documentation in your account that looks like the following:

{% hint style="danger" %}
Example: do not use on productive systems!
{% endhint %}

| DNS Type | DNS Domain        | IP Address      |
| -------- | ----------------- | --------------- |
| A-RECORD | 123abc.myhero.com | 123.123.123.123 |

Simply copy your individual settings from your JENTIS account to your hosting DNS entries and select "A RECORD" to define the details. You will find this information by creating a new container or editing an existing one:

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2F1DDkVSF2RU9EDgaHhYFW%2Fimage.png?alt=media&amp;token=18338e5e-3844-4e3f-afe9-e9aff262a26f" alt=""><figcaption></figcaption></figure>

Once you add the DNS A Record, we will automatically verify the configuration in up to 30 minutes. Alternatively, you can return to your container’s configuration and click on **Verify**.

You can always check the status of your DNS Entry on your container’s configuration:

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FGZlxyvdnpqctCL8nXLhc%2Fimage.png?alt=media&amp;token=78d5f224-19c3-4d15-ba93-b5e0de39cd0c" alt=""><figcaption></figcaption></figure>

***

If you have any questions or suggestions, contact us through our [Helpdesk](https://jentis.atlassian.net/servicedesk/customer/portal/1).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/getting-started/quickstart/make-tracking-first-party-set-your-dns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
