Bobcares

How to Add a DNS Record Using the OVH API

by | May 15, 2024

Learn how to add a DNS record with OVH API. Our OVH Support team is here to help you with your questions and concerns.

How to Add a DNS Record Using the OVHcloud API

Did you know that adding a DNS record via the OVH API is a great way to manage domain settings programmatically?

In fact, with the OVH DNS Management API, we can add, update, or delete our domain’s DNS records hosted on OVH’s infrastructure.

ovh api add dns record

Our experts have put together this guide to help you out.

Before we begin, make sure we have the following:

  • An API key (Consumer Key and Application Secret) created via the OVHcloud Control Panel.
  • Also, identify the zone name where we want to add the record. We can find this in the OVHcloud Control Panel under the DNS management section for our domain.

Now, let’s get started:

  1. The API endpoint for adding a DNS record follows this structure:

    PUT /domain/zone/{zoneName}/record

    Remember to replace `{zoneName}` with the DNS zone’s name.

    Furthermore, the request body should be a JSON object with information about the record:

    {
    "subDomain": "{subDomain}", // Optional subdomain for the record (e.g., "www")
    "recordType": "{recordType}", // Type of record (e.g., "A", "AAAA", "MX", etc.)
    "target": "{targetValue}", // Target value for the record (e.g., IP address for A record)
    "priority": "{priority}" // Optional priority for MX records (lower number = higher priority)
    }

    We have to replace the placeholders with the corresponding specific values.

  2. Then, create a signature string following the OVHcloud API signature process with the Application Secret.
  3. Also, send a PUT request to the constructed API endpoint with a tool like `curl` or an HTTP client library in our programming language. We have to include the generated signature string within the request header, usually under `X-Ovh-Consumer`.

    Additionally, include the JSON object with the record details in the request body.

    Here’s an example using `curl`:

    curl -X PUT https://api.ovh.com/1.0/domain/zone/{zoneName}/record \
    -H "Content-Type: application/json" \
    -H "X-Ovh-Application: {yourApplicationKey}" \
    -H "X-Ovh-Timestamp: {currentTimestamp}" \
    -H "X-Ovh-Signature: {generatedSignature}" \
    -H "X-Ovh-Consumer: {consumerKey}" \
    -d '{
    "subDomain": "www",
    "recordType": "A",
    "target": "122.44.63.88",
    "priority": 0
    }'

  4. Now, the OVHcloud API returns a response about the success (status code 200) or failure. If it is a failure, the response will include an error code and details. We can handle the response to make sure the DNS record has been added successfully.

With the above steps, we can easily manage our DNS records using the OVHcloud API. We can also streamline our domain management tasks and integrate them into automated workflows.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to add a DNS record with OVH API.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF