Create and manage a Reverse DNS record
Notes:
Only contract administrators, owners, and users with accessAndManageDns privilege can create and manage DNS zones and DNS records via the API. You can also set User privileges in the DCD.
Sub-users can create Reverse DNS records only if the user group they belong to has access to the concerned IP block. For more information, see Add users to a group.
Currently, the Cloud DNS API supports only IPv4 addresses for Reverse DNS records.
To create a reverse DNS entry for IPv6 addresses, please contact IONOS Cloud Support.
Prerequisites
You need an IONOS Cloud account with API credentials configured with the appropriate permissions.
Before creating a Reverse DNS record, you must create an A record for the IP address you want to use for the reverse DNS record. For more information, see Create a DNS Record.
To create a Reverse DNS Record with Cloud DNS API, follow this step:
Perform a POST request with name, a description of reverse DNS record (optional), and the IP.
Note: The IP address must be from a reserved IP range. To reserve an IP address, click Menu > Management > IP Management. Enter a name and the number of IP addresses, and select a region where you want your IP addresses to be reserved. Click Reserve IP to reserve the IP address, and confirm the reservation by pressing OK.
Result: On a successful POST request, you receive a response containing the reverse DNS record UUID, type, href, metadata, properties of your reverse DNS record, name, description, and IP address.
Request
Response
200 Successful operation
Response Fields
Field | Type | Description | Example |
---|---|---|---|
id | string | UUID of the newly created reverse DNS record | 2a4428b3-dbe0-4357-9c02-609025b3a40f |
createdDate | string | Reverse DNS record creation timestamp | 2023-03-15T09:58:59.147746133Z |
lastModifiedDate | string | Reverse DNS record update timestamp | 2023-03-15T09:58:59.147746133Z |
name | string | Name of the reverse DNS record | mail.example.com |
description | string | Description of the reverse DNS record | The reverse DNS record is used for mail.example.com |
ip | string | IP address of the reverse DNS record | |
type | string | Type of the reverse DNS record | reverserecord |
href | string | URL to the reverse DNS record |
Retrieve all reverse DNS records
To retrieve all reverse DNS records, perform a GET request to the /reverserecords
endpoint.
Result: On a successful GET request, you receive a response containing all reverse DNS records.
Request
Response
200 Successful operation
Response Fields
Field | Type | Description | Example |
---|---|---|---|
id | string | UUID of the reverse DNS record | 2a4428b3-dbe0-4357-9c02-609025b3a40f |
createdDate | string | Reverse DNS record creation timestamp | 2023-03-15T09:58:59.147746133Z |
lastModifiedDate | string | Reverse DNS record update timestamp | 2023-03-15T09:58:59.147746133Z |
name | string | Name of the reverse DNS record | mail.example.com |
description | string | Description of the reverse DNS record | The reverse DNS record is used for mail.example.com |
ip | string | IP address of the reverse DNS record | |
type | string | Type of the reverse DNS record | reverserecord |
href | string | URL to the reverse DNS record |
Retrieve a reverse DNS record
To retrieve a reverse DNS record, perform a GET request to the /reverserecords/{id}
endpoint.
Result: On a successful GET request, you receive a response containing the reverse DNS record UUID, type, href, metadata, and properties of your reverse DNS record, name, description, and IP.
Request
Response
200 Successful operation
Response Fields
Field | Type | Description | Example |
---|---|---|---|
id | string | UUID of the reverse DNS record | 2a4428b3-dbe0-4357-9c02-609025b3a40f |
createdDate | string | Reverse DNS record creation timestamp | 2023-03-15T09:58:59.147746133Z |
lastModifiedDate | string | Reverse DNS record update timestamp | 2023-03-15T09:58:59.147746133Z |
name | string | Name of the reverse DNS record | mail.example.com |
description | string | Description of the reverse DNS record | The reverse DNS record is used for mail.example.com |
ip | string | IP address of the reverse DNS record | |
type | string | Type of the reverse DNS record | reverserecord |
href | string | URL to the reverse DNS record |
Modify a reverse DNS record
To modify a reverse DNS record, perform a PUT request to the /reverserecords/{id}
endpoint.
Result: On a successful PUT request, you receive a response containing the reverse DNS record UUID, type, href, metadata, and properties of your reverse DNS record, name, description, and IP.
Request
Response
200 Successful operation
Response Fields
Field | Type | Description | Example |
---|---|---|---|
id | string | UUID of the reverse DNS record | 2a4428b3-dbe0-4357-9c02-609025b3a40f |
createdDate | string | Reverse DNS record creation timestamp | 2023-03-15T09:58:59.147746133Z |
lastModifiedDate | string | Reverse DNS record update timestamp | 2023-03-15T09:58:59.147746133Z |
name | string | Name of the reverse DNS record | mail.example.com |
description | string | Description of the reverse DNS record | The reverse DNS record is used for mail.example.com |
ip | string | IP address of the reverse DNS record | |
type | string | Type of the reverse DNS record | reverserecord |
href | string | URL to the reverse DNS record |
Delete a reverse DNS record
To delete a reverse DNS record, perform a DELETE request to the /reverserecords/{id}
endpoint.
Result: On a successful DELETE request, you receive a HTTP response 202 Successful operation.
Request
Response
202 Successful operation
Quota
To retrieve the quota of reverse DNS records, perform a GET request to the /quota
endpoint.
Result: On a successful GET request, you receive a response containing the quota limits and quota usage for your contract.
Request
Response
200 OK
Response Fields
Field | Type | Description | Example |
---|---|---|---|
records | string | Number of DNS records | 100000 |
reverseRecords | string | Number of reverse DNS records | 5000 |
secondaryZones | string | Number of secondary DNS zones | 100000 |
zones | string | Number of DNS zones | 50000 |
records | string | Number of DNS records used | 9 |
reverseRecords | string | Number of reverse DNS records used | 1 |
secondaryZones | string | Number of secondary DNS zones used | 6 |
zones | string | Number of DNS zones used | 5 |
Last updated