> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/primary-zone/create-dns-records.md).

# Create DNS Records

IONOS Cloud DNS: create DNS records in a primary zone using the DCD

{% hint style="info" %}
**Prerequisites:**

* A primary zone is mandatory to create a record. For more information, see [<mark style="color:blue;">Create Primary Zones</mark>](/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/primary-zone/create-primary-zone.md).
* Only contract administrators, owners, and users with **Access and manage DNS** privilege can create and manage primary and secondary zones and records. You can set user privileges in the [<mark style="color:blue;">DCD</mark>](/cloud/network-services/cloud-dns/dcd-how-tos/set-user-privileges.md) or using the [<mark style="color:blue;">API</mark>](/cloud/network-services/cloud-dns/api-how-tos/set-user-privileges-api.md).
  {% endhint %}

To create a record, follow these steps:

1\. In the **DCD**, go to **Menu** > **Network Services** > **Cloud DNS** > **Public zones** tab.

2\. Select **Primary Zones** from the drop-down list.

3\. Select the appropriate primary zone in the **DNS ZONES** column to create records. Alternatively, click **Details & Records** in the **ACTIONS** column.

![Zone selection](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-85b510ea4adb54496925ce3dbaebb38f8505ebfe%2Fzones-overview.png?alt=media)

4\. Click **Create record** in the **Details & Records** window.

5\. Enter the following details in the **Create Record** window:

* **Enabled/Disabled:** Set it to either **Enabled** (by default) or **Disabled**.
* **Name:** Enter an appropriate name for your DNS record. Leaving the name field empty will result in the creation of an Apex record. You can also provide `*` to create a wildcard DNS record.
* **TTL:** Enter an appropriate Time-To-Live (TTL) setting in seconds for your DNS record. The default value is 3600 seconds.
* **Type:** Select one of the following record types: `A`, `AAAA`, `MX`, `CNAME`, `TXT`, `NS`, `SRV`, `ALIAS`, `CAA`, `CERT`, `DS`, `SOA`, `HTTPS`, `LOC`, `OPENPGPKEY`, `RP`, `SMIMEA`, `SSHFP`, `SVCB`, `TLSA`, and `URI`.
* **Content:** Enter the content appropriate to the selected record type.
* **Preview:** Ensure that the details of the record to be created are accurate.&#x20;

![Define record properties](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-122b661ae3113405edca82ff8153686e1a1b65f4%2Fcreate-record-properties.png?alt=media)

6\. Click **Save** to create the DNS record.

{% hint style="success" %}
**Result:** Your DNS record is now created.
{% endhint %}


---

# 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.ionos.com/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/primary-zone/create-dns-records.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.
