> For the complete documentation index, see [llms.txt](https://docs.up-network.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.up-network.ch/documentation/en/guides/rdns-ptr.md).

# Configure reverse DNS (rDNS / PTR)

Reverse DNS maps an IP address to a hostname using a PTR record. You can configure it yourself in the UP-NETWORK client portal for a **VPS, dedicated server or network service**, including additional addresses assigned to that service.

## Prepare the hostname before the PTR

Choose a fully qualified hostname, such as `server.example.com`, and first create its record in the authoritative DNS zone for your domain. For PTR validation to succeed, **this hostname must already resolve to the IP address concerned**:

| Address to configure | Desired PTR hostname | DNS record to create first              |
| -------------------- | -------------------- | --------------------------------------- |
| IPv4: `192.0.2.10`   | `server.example.com` | `server.example.com. A 192.0.2.10`      |
| IPv6: `2001:db8::10` | `server.example.com` | `server.example.com. AAAA 2001:db8::10` |

These values are examples: replace them with your hostname and addresses. **A is for IPv4; AAAA is for IPv6.** An A record alone does not validate the PTR of an IPv6 address. If you use the same hostname for both families, prepare both its A and AAAA records.

Check the public DNS response before continuing. If the hostname uses a proxy or CDN, its response may contain the proxy’s IP instead of your service’s IP: use a hostname that resolves directly to the address concerned. The [Domains and DNS guide](https://docs.up-network.ch/documentation/en/guides/domains-and-dns.md) explains where to edit your zone.

## Open Reverse DNS in the client portal

1. Log in to your [client portal](https://manager.up-network.ch/billmgr).
2. Under **Products/Services**, open the category for your VPS, dedicated server or network service, then tick the row of the service concerned.
3. Click **Reverse DNS** in the action toolbar. The **Server reverse DNS** list shows the IP addresses and their current **PTR hostname**.

![Tick the service and click Reverse DNS.](https://3018019429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSSjc1d2nxCIyxVmez9eI%2Fuploads%2FP5pDmJBzVooiVJF5M67M%2Fselect-service.png?alt=media)

The screenshot shows a VPS; the same principle applies to the other services concerned.

## Set or edit the PTR of a listed IP

1. Select the row of the IPv4 or IPv6 address to edit.
2. Click **Set / edit PTR**.
3. Enter the fully qualified hostname prepared in DNS, such as `server.example.com`, then save. Enter a hostname without `https://`, a port or a path.

**Additional IPv4 addresses** assigned to the service are configured the same way: select each address and set its PTR. The chosen hostname must have an A record pointing to that specific IPv4 address.

![In Server reverse DNS, use Set / edit PTR or Add IPv6 PTR as appropriate for the address.](https://3018019429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSSjc1d2nxCIyxVmez9eI%2Fuploads%2FWL9TX0Bldfmiy3UR5xBc%2Fmanage-ptr.png?alt=media)

## Add the PTR of an additional IPv6 address

If the IPv6 address already appears in the list, use **Set / edit PTR**. For an additional IPv6 address without an entry yet:

1. First create an **AAAA** record from the desired hostname to that IPv6 address.
2. In **Server reverse DNS**, click **Add IPv6 PTR**.
3. Enter the full IPv6 address assigned to your service and its matching hostname, then save.

A PTR applies to a **full IPv6 address**, not a prefix such as a `/64`. Repeat for each additional address you want to publish. Use only addresses and prefixes assigned to your service.

## Verify the result

Configuration is performed in the client portal after forward DNS validation, without asking support to create the PTR manually. DNS caches may still retain an older value until its TTL expires.

From a terminal with `dig`, check both directions using your own values:

```sh
dig +short A server.example.com
dig +short AAAA server.example.com
dig +short -x 192.0.2.10
dig +short -x 2001:db8::10
```

The A and AAAA queries must contain the IPv4 and IPv6 addresses concerned, respectively. Each reverse query must return the configured hostname, possibly with a trailing dot. Setting the PTR does not automatically create your domain’s A or AAAA records.

## If validation is rejected

* Check the fully qualified hostname entered and the presence of an **A record for IPv4**, or an **AAAA record for IPv6**, pointing to the correct address.
* Check the zone actually used by the domain’s nameservers and the public response, not just the value shown in your DNS editor.
* After a recent change, allow caches to expire and try again. Do not replace the required IP with that of a proxy or another service.
* If an assigned address is missing from the list or rejection persists, open a [support ticket](https://docs.up-network.ch/documentation/en/guides/how-to-open-a-support-ticket.md) with the service, IP, requested hostname, error message and your DNS results.

Updated on 19 October 2026. Workflow and screenshots supplied by UP-NETWORK.
