For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt, and this page is available as Markdown at https://docs.ovhcloud.com/en/guides/public-cloud/compute/setup-instance-reverse.md.
Skip to content
Appearance
Console(the OVHcloud Console, opens in a new tab)

How to configure reverse DNS for a Public Cloud instance

View as Markdown

Find out how to set up the reverse DNS resolution of your OVHcloud Public Cloud instance

Objective

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.

This guide explains how to configure the reverse DNS path for the IP address(es) of your Public Cloud instance.

Requirements

  • A Public Cloud instance in your OVHcloud account
  • A domain name with its A record mapped to the instance

OVHcloud Console Access

  • Direct link:
  • Navigation path: Bare Metal Cloud > Network > IP addresses

Instructions

The Filter by service... list on the IP addresses page allows you to filter your IP addresses by service: select your Public Cloud project in the Public Cloud group. You can also search for a specific IP in the search bar.

Click on the IP address concerned, then open the Reverse DNS tab and click Configure.

In the Configure Reverse DNS window, enter your reverse path in the Reverse DNS hostname field and click on Configure.

To delete a reverse path, click the delete icon in the row of the reverse in the Reverse DNS tab.

Info

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.

If the domain name is managed by OVHcloud as its registrar and it uses OVHcloud DNS servers, you can refer to this guide.

Go further

First steps with Public Cloud instances

How to edit an OVHcloud DNS zone

Join our community of users.

Was this page helpful?