---
title: "How to configure reverse DNS for a Public Cloud instance"
description: "Reverse DNS (rDNS) is the complement to \"forward\" DNS resolution, which resolves domain names into IP addresses. With reverse DNS resolution, an IP address can"
url: https://docs.us.ovhcloud.com/en/public-cloud/compute/setup-instance-reverse
lang: en
---
> For AI agents: the complete documentation index is available at https://docs.us.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.us.ovhcloud.com/en/llms-full.txt.

# How to configure reverse DNS for a Public Cloud instance

Reverse DNS (_rDNS_) is the complement to "forward" DNS resolution, which resolves domain names into IP addresses. With reverse DNS resolution, an IP address can resolve into the domain name (or host name) it is mapped to. This means that DNS queries of the associated IP address will return this domain name.

Configuring the reverse DNS resolution for an instance is especially useful when sending emails. A mail server's validation by spam protection systems will improve if a DNS lookup of the IP address resolves properly.

 

## Requirements

- A [Public Cloud instance](https://us.ovhcloud.com/public-cloud/) in your OVHcloud account
- A domain name with its `A` record pointing to the instance

#### OVHcloud Control Panel Access

- **Direct link:** [Network IPs](https://manager.us.ovhcloud.com/#/network/ip)
- **Navigation path:** `Bare Metal Cloud` > `Network` > `IP`

 

## Instructions

Once you see your list of IPs, you can filter for your Public Cloud project ID using the drop-down menus above the table.

In the table, select the _more options_ `...` button in the row of an eligible service and select `Configure the reverse DNS`.

In the new window, enter your reverse path and click on `Confirm`.

You can also edit the reverse path directly via the icon in the **Reverse DNS** column of the table.

**Note:**

If the modification does not work as expected, verify that the `A` record is correctly configured in the DNS zone of your domain name. Bear in mind that it might take up to 24 hours for DNS zone changes to be effective, in case you have only recently edited the `A` record.

 

## Go further

Browse all the [Compute guides](https://docs.us.ovhcloud.com/en/public-cloud/compute/landing-page-compute.md).

Browse the rest of the [OVHcloud US documentation](https://docs.us.ovhcloud.com/en/index.md) for guides on our other products and services.

Learn more about [Public Cloud Compute](https://us.ovhcloud.com/public-cloud/compute/) on the OVHcloud US website.