> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/connectivity/domains-and-dns/how-tos/manage-dns-records.md).

# Manage DNS records

***

## Manage DNS records using the control panel

In the overview of the DNS service, click **Manage** next to the domain name for which you want to manage DNS records.

Here, you can also see whether Glesys DNS is being used at the registrar under *Nameservers*. Under *Registrar*, we can see if Glesys or another provider is the registrar for the domain.

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

Here, you can manage the DNS for the domain name.

To delete a record from the DNS, click the red cross to the right of the record.

To create new records, click **Add record** at the top right of the page. In the menu that opens, select the type of record you want to create.

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

In this example, we choose to add an A record. An A record points a hostname to an IPv4 address. For descriptions of other types of records, see [Different types of records](#different-kinds-of-records).

Once you select the record type, a new empty row is added under the current record type.

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

You can choose an existing server at Glesys to point the hostname to by selecting the server from the dropdown menu under Data. Alternatively, you can manually enter an IPv4 address for the record.

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

In the example above, three A records have been created for the domain *example.com*. The first record, *@*, points to a server at Glesys named *web1*. An @ character in the *Host* field indicates that the record applies to the root of the domain, which in this case is *example.com*. Therefore, *example.com* points to the server *web1* with the IP address 203.0.113.110.

The second record, *lab*, also points to the same server, *web1*. The full hostname is thus *lab.example.com*.

The third record, *voip.example.com*, points to the IP address 203.0.113.99. In this case, the IP address was entered manually.

The TTL value in the example is set to 3600 seconds for all hosts. TTL stands for *Time To Live* and specifies for how long other DNS servers—such as those at an ISP or local DNS servers in firewalls—can cache the hostname. After this time, 3600 seconds in the example, those DNS servers must refresh the value from Glesys DNS when a new query is made for that hostname.

The *Host* field represents the hostname being created under the domain *example.com*. TTL specifies how long other DNS servers can cache the information. The *Data* field is the value, such as an IP address, that the hostname points to.

### Different kinds of records

There are many different types of records. Below are the record types supported by Glesys, along with examples.

For most record types, you can use an @ character in the *Host* field to point to the root domain, such as *example.com*. The root domain is also referred to as the apex domain or sometimes as the bare domain.

Keep in mind that when specifying complete hostnames (FQDN, *Fully Qualified Domain Name*) in the *Data* field, these must end with a period to indicate the top of the DNS hierarchy.

#### A record

A records (Address) are used to point a hostname to an IPv4 address.

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

#### AAAA record

AAAA records (*4 x Address*) are used to point a hostname to an IPv6 address.

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

#### ALIAS record

ALIAS records are used in a similar way to *CNAME* records, but *ALIAS* records also work for the root domain, such as *example.com*. Note that ALIAS records are not officially standardized, as there is currently no RFC for them.

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

#### CAA record

CAA records (*Certification Authority Authorization*) are used to inform certificate authorities (CAs) whether they are allowed to issue certificates for the domain in question. In this example, only Let's Encrypt is permitted to issue certificates for the domain, and any violations should be reported to the email address *<security@example.com>*.

However, note that it is not mandatory for a CA to report violations. They are, however, prohibited from issuing a certificate if they are not listed. If the flag (set to `0` in this case) is changed to `1`, the CA must understand the complete record. This means that if the record is incorrect or cannot be interpreted, the CA is not allowed to issue a certificate if the flag is set to `1`.

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

#### CNAME record

CNAME records (*Canonical Name*) are a type of alias. Instead of pointing a hostname to an IP address, a CNAME points to another hostname. It is common to use a CNAME record for www to point to the apex domain, i.e., the root domain.

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

#### MX record

MX records (*Mail eXchanger*) are used to specify which email servers are used for the domain. The sending email server looks at the MX records for the domain to determine which server the email should be delivered to.

The priority field indicates which server should be prioritized. A lower number means higher priority. If the fields have the same value, the emails will be distributed equally among the servers.

In Glesys DNS, MX records also have a button labeled **Templates**. Under this, there is an option for **Glesys**. Clicking this button will automatically populate the MX records with Glesys email servers.

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

#### NS record

NS records (*Name Server*) are used to list the domain's name servers (DNS servers).

This record type also includes a button labeled **Templates** with an option for **Glesys**. Clicking this button will automatically populate the NS records with Glesys DNS servers.

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

#### PTR record

PTR records (*Pointer*) are used to resolve an IP address to a hostname. This is the opposite of an A record.

You set PTR records for Glesys IP addresses under **IP addresses** in the control panel by clicking the pencil icon next to the relevant IP address.

To use PTR records in Glesys DNS with IP ranges purchased from other providers, please get in touch with Glesys support.

#### SRV record

SRV records (*Service*) are a special type of record. In this record, we specify the type of service, protocol, priority, weight, port number, and target. Not all network protocols support SRV records.

Under the **Templates** button, you find templates for services like Google Talk and Microsoft Lync Online.

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

#### TXT record

TXT records (*Text*) are used to specify various types of text strings. For example, they are used for SPF (*Sender Policy Framework*) to restrict who is allowed to send email from a specific domain. TXT records are also used for various types of verification strings, such as for Google Workspace.

Under the **Templates** button, you can find ready-made templates for SPF records for Glesys email as well as Google Workspace/Gmail.

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

#### URL record

URL records (*URL*) are a special type of record that works with web addresses. This is not a standardized record type, and no RFC exists for it. The record redirects a web request to another address using HTTP code 301 (*Moved Permanently*).

In the *Data* field, you specify the web address to which the hostname should be redirected, including the HTTP part. However, do not include a period after the domain. The reason for this is that this is not a true DNS record but rather a form of redirection.

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

#### SOA record

An SOA record should already exist and cannot be added using the **Add record** button. However, it can still be helpful to understand how this record functions.

*Primary nameserver*: This is the nameserver from which secondary name servers retrieve their information.

*Responsible person*: This is the email address of the person responsible for the zone's DNS. In this case, it is <registry@glesys.se>. Note that the @ symbol is replaced with a dot in this field.

*Refresh*: This is the time in seconds that the secondary servers should wait before fetching updated information about the SOA record from the primary server.

*Retry*: This is the time in seconds that the secondary name servers should wait before trying to contact the primary server again in case of issues.

*Expire*: If a secondary server has not received a response from the primary server after the time specified in *Expire*, it should stop responding to queries for the zone.

*Minimum*: Specifies a default time (TTL) for how long other servers are allowed to cache information about the zone if the specific records do not have their own TTL (*Time To Live*).

The SOA record for Glesys looks as follows.

### Necessary DNS records for a domain

There are some essential records you need to create for the DNS to function correctly for your domain name. These include NS records (*Name Server*) that point to all DNS servers for the domain. Additionally, you need to create an SOA record (*Start of Authority*), which contains important information about the DNS and the domain.

If you chose to create Glesys standard records when adding the domain, this is already done. If not, you need to create the following NS and SOA records.

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

Note, however, that you do not need to create these records if they already exist. The SOA record should already be present.&#x20;

You can create an NS record by clicking **Add record** at the top of the page and choosing **NS record** from the menu.

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

After that, you can select **Templates** and then **Glesys** in the box for NS records. This will automatically create the necessary records for you.

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

## Manage DNS records using the API

* To list all the current records for a domain using the [API](/platform/control-panel/api.md), use the [domain/listrecords](https://github.com/GleSYS/API-docs/wiki/API-Documentation#domainlistrecords) endpoint.
* To add a new record, use the [domain/addrecord](https://github.com/GleSYS/API-docs/wiki/API-Documentation#domainaddrecord) endpoint.
* To update an existing record, use the [domain/updaterecord](https://github.com/GleSYS/API-docs/wiki/API-Documentation#domainupdaterecord) endpoint.
* To delete a record, use the [domain/deleterecord](https://github.com/GleSYS/API-docs/wiki/API-Documentation#domaindeleterecord) endpoint.


---

# 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:

```
GET https://docs.glesys.com/products/connectivity/domains-and-dns/how-tos/manage-dns-records.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.