IONOS Cloud DNS lets you publish Domain Name System (DNS) zones of your domains and subdomains on public Name Servers. You can manage your DNS zones and records via the Cloud DNS API.

With IONOS Cloud DNS, you can import and export DNS zone files, create secondary DNS zones, enable DNSSEC keys for DNS zones, and manage DNS records. You can also use the Cloud DNS API to create and manage Reverse DNS records for your IPv4 addresses.

The IONOS Name Server infrastructure is distributed across 14 point-of-presence (POP) locations in Europe and the USA to ensure fast and reliable DNS resolution for users across these locations.

Product Overview

Developer Tools

Recommended How-To's

The Cloud DNS API lets you manage DNS zones and records programmatically using conventional HTTP requests.

On successful registration of the domain name, you can now assign more users with the privilege to manage DNS zones and records via the API. By default, only contract owners and administrators have permission to use the Cloud DNS API.

To set user privileges via the API, see Set User Privileges via the API.

On assigning user privileges, continue with the following API How-Tos:

• Create a DNS Zone

• Create a DNS Record

• Connect Domain Name to Cloud DNS

• Create and manage a Reverse DNS record

If you already have a primary zone hosted elsewhere, you can Create a Secondary DNS Zone to improve reliability, redundancy, load balancing, and performance.

Additionally, try the following features for your primary zones hosted in Cloud DNS:

• Perform PUT Request for Non-Existing Records

• Import a DNS Zone

• Export a DNS Zone

• Create a Secondary DNS Zone

• Manage DNSSEC Signing Keys

To create a DNS zone with Cloud DNS API, follow this step:

• Perform a POST request with the domain or subdomain, a description of your DNS zone (optional), and the DNS zone status (enable), true or false.

Request

curl --location \  
--request POST  'https://dns.de-fra.ionos.com/zones' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJraWQiO' \
--header 'Content-Type: application/json' \
--data '{
   "properties": {
    "zoneName": "example.com",
     "description": "example of zone creation",
     "enabled": true
    }
}'

Response

202 Successful operation

{
    "id": "2a4428b3-dbe0-4357-9c02-609025b3a40f",
    "metadata": {
        "createdDate": "2023-03-15T09:58:59.147746133Z",
        "lastModifiedDate": "2023-03-15T09:58:59.14774631Z",
        "nameservers": [
            "ns-ic.ui-dns.com",
            "ns-ic.ui-dns.de",
            "ns-ic.ui-dns.org",
            "ns-ic.ui-dns.biz"
        ],
        "state": "CREATED"
    },
    "properties": {
	       "zoneName": "example.com",
        "description": "example of zone creation",
        "enabled": true
    }
}

Response Fields

Quota

To retrieve the quota of DNS zones, perform a GET request to the /quota endpoint.

Request

curl --location 'https://dns.de-fra.ionos.com/quota' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJraWQiO' \
--header 'Content-Type: application/json'

Response

200 OK

{
  "quotaLimits": {
    "records": 100000,
    "reverseRecords": 5000,
    "secondaryZones": 100000,
    "zones": 50000
  },
  "quotaUsage": {
    "records": 9,
    "reverseRecords": 1,
    "secondaryZones": 6,
    "zones": 5
  }
}

Response Fields

You can import a DNS zone from your existing DNS provider to IONOS Cloud.

To import an existing zone to IONOS Cloud DNS, follow these steps:

1. Create a DNS zone without records.

2. Perform a PUT request providing the zoneId of the newly created zone and the zone file.

Request

Response

200 Successful operation

Zone file

The imported file has to be in BIND format, a widely used format supported by most DNS software, including the popular BIND DNS server.

The file should include all the record types associated with the selected zone. The Start of Authority (SOA) and Name Server (NS) records are not to be considered since IONOS Cloud uses its name server configuration.

Similar to retrieving a DNS zone, you need to provide the UUID of the DNS zone that you want to export.

To export an existing zone at IONOS Cloud DNS in a BIND format, follow this step:

• Perform a GET request providing the zoneId of your zone.

Request

Response

200 Successful operation

Zone file

The exported zone file is in BIND format, a widely used format supported by most DNS software, including the BIND DNS server.

The file includes all record types associated with the selected zone, including SOA record, NS record, Service (SRV) record, and configuration information such as TTL values.

An example of a file in BIND format with an updated SRV record is as follows:

To facilitate additional users with permissions to manage the DNS zones and records, the offers a new group privilege called Access and manage DNS in the User Manager, under the Privileges tab. You can grant this privilege to a group via the . By giving this privilege to a group, all users in this group get permission to manage the Cloud DNS zones and records via the Cloud DNS API.

For information on setting Access and manage DNS privilege to a group, see .

Prerequisites

To create a Reverse DNS Record with , follow this step:

• Perform a POST request with name, a description of reverse DNS record (optional), and the IP.

Request

Response

200 Successful operation

Response Fields

Retrieve all reverse DNS records

To retrieve all reverse DNS records, perform a GET request to the /reverserecords endpoint.

Request

Response

200 Successful operation

Response Fields

Retrieve a reverse DNS record

To retrieve a reverse DNS record, perform a GET request to the /reverserecords/{id} endpoint.

Request

Response

200 Successful operation

Response Fields

Modify a reverse DNS record

To modify a reverse DNS record, perform a PUT request to the /reverserecords/{id} endpoint.

Request

Response

200 Successful operation

Response Fields

Delete a reverse DNS record

To delete a reverse DNS record, perform a DELETE request to the /reverserecords/{id} endpoint.

Request

Response

202 Successful operation

Quota

To retrieve the quota of reverse DNS records, perform a GET request to the /quota endpoint.

Request

Response

200 OK

Response Fields

If you have an infrastructure that uses public DNS records and manage it by defining the required state, you can use Cloud DNS as follows:

1. with Cloud DNS.

2. Generate a UUID (v3, v4, and v5 supported) for your DNS record.

3. Add to your infrastructure a PUT call for the desired record configuration with your UUID and assign it to the corresponding DNS zone ID.

Request

Response

202 Successful operation

Response Fields

To connect your domain name to the IONOS Cloud DNS zone that you created, specify the IONOS Cloud DNS nameservers as the domain's authoritative nameservers.

To connect a domain nameserver to a DNS zone, follow these steps:

1. for your domain and the associated DNS records.

2. Save the four nameservers Cloud DNS provided upon creating the DNS zone.

3. Go to your Domain Registrar and update your domain's nameservers with the four nameservers from the previous step.

ExternalDNS Overview

ExternalDNS is an open-source tool that automates the management of public DNS records for Kubernetes resources such as services and ingresses, that are publicly exposed outside the cluster.

The ExternalDNS solution offers the following capabilities:

• Control to developers to manage DNS resources that are usually managed manually by third teams. Example: Infrastructure team.

• Ensures that the DNS records are always up-to-date with the current state of the Kubernetes cluster.

• Manages a large number of records automatedly.

• Simplifies the management of DNS records with improved security.

Deployment of ExternalDNS on Managed Kubernetes

Follow these steps to set up ExternalDNS for your Managed Kubernetes with IONOS DNS Provider Cloud DNS:

1. Prepare domain name: You need to first Create a DNS Zone for your domain name with Cloud DNS and then Connect Domain Name to Cloud DNS.

2. Add Helm chart: Add the Bitnami Helm repository, which contains the official external-dns Helm chart.

helm repo add bitnami https://charts.bitnami.com/bitnami

1. Create configuration: Create values file for ExternalDNS Helm chart that includes the plugin configuration. In this example, the values file is called external-dns-ionos-values.yaml.

# OCI image of ExternalDNS that contains the plugin provider feature
image:
  registry: ghcr.io
  repository: ionos-cloud/external-dns-plugin-provider
  tag: latest

# Modify how DNS records are synchronised between sources and providers (default: sync, options: sync, upsert-only, create-only)
policy: sync

# provider needs to be set to plugin
provider: plugin

# url of the provider which the external-dns will target
extraArgs:
  plugin-provider-url: http://localhost:8888

# plugin is deployed as sidecar
sidecars:
  - name: ionos-plugin
    image: ghcr.io/ionos-cloud/external-dns-ionos-plugin:latest
    ports:
      - containerPort: 8888
        name: http
    livenessProbe:
      httpGet:
        path: /health
        port: http
      initialDelaySeconds: 10
      timeoutSeconds: 5
    readinessProbe:
      httpGet:
        path: /health
        port: http
      initialDelaySeconds: 10
      timeoutSeconds: 5
    env:
      # Set port of plugin (value needs to match the container port and plugin provider url port, default value: 8888)
      - name: SERVER_PORT
        value: "8888"
      # Listen on all interfaces for kubernetes probes
      - name: SERVER_HOST
        value: ""
      # Limit possible target zones by a domain suffix (optional)
      - name: DOMAIN_FILTER
        value: "example1.com,example2.com"
      # Exclude subdomains (optional)
      - name: EXCLUDE_DOMAIN_FILTER
        value: "example3.com"
      # Limit possible domains and target zones by a Regex filter. Overrides domain-filter (optional)
      - name: REGEXP_DOMAIN_FILTER
        value: ".*.example4.com"
      # Regex filter that excludes domains and target zones matched by regex-domain-filter (optional)
      - name: REGEXP_DOMAIN_FILTER_EXCLUSION
        value: ".*.example5.com"
      # When enabled, prints DNS record changes rather than actually performing them (default: false)
      - name: DRY_RUN
        value: "true"         
      # Token for DNSaaS rest API authentication (mandatory)  
      - name: IONOS_API_KEY
        value: "21215454"
      - name: LOG_LEVEL
        value: debug
      # When enabled debug logs for the DNSaaS rest API are enabled (default: false)  
      - name: IONOS_DEBUG
        value: "true"

1. Install ExternalDNS: To install ExternalDNS with Bitnami Helm chart, use the following commad:

helm install external-dns-ionos bitnami/external-dns -f external-dns-ionos-values.yaml

1. Deploy application: Follow this step to deploy an application:

• Deploy an echo server application by using the file echoserver_app.yaml.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: echoserver
  namespace: echoserver
spec:
  replicas: 1
  selector:
    matchLabels:
      app: echoserver
  template:
    metadata:
      labels:
        app: echoserver
    spec:
      containers:
      - image: ealen/echo-server:latest
        imagePullPolicy: IfNotPresent
        name: echoserver
        ports:
        - containerPort: 80
        env:
        - name: PORT
          value: "80"
---
apiVersion: v1
kind: Service
metadata:
  name: echoserver
  namespace: echoserver
spec:
  ports:
    - port: 80
      targetPort: 80
      protocol: TCP
  type: ClusterIP
  selector:
    app: echoserver
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: echoserver
  namespace: echoserver
  annotations:
    kubernetes.io/ingress.class: nginx
spec:
  rules:
  - host: app.example1.com #This is your subdomain / record name
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: echoserver
            port:
              number: 80

If you want to use a service, you do not need to install an ingress controller. You can install an ingress controller in the cluster and deploy the application with kubectl by using the following command:

kubectl apply -f echoserver_app.yaml

Verify deployment

You can verify that the application deployed is functioning as expected by using one of the following options.

Access application

Check that the echo server app runs on the subdomain you have specified by using the following command:

curl -I app.example1.com/?echo_code=404-300

Expected result:

HTTP/1.1 404 Not Found 
HTTP/1.1 300 Multiple Choices

Check DNS records

Check that the new A and TXT records are created by using the following command:

curl --location --request GET 'https://dns.de-fra.ionos.com/records?filter.name=app' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJraWQiOiI4MmE5' \
--data ''

To set user privileges using the Cloud API for managing DNS zones and records, follow these steps:

1. Authenticate to the Cloud API using your API credentials.

2. Create a user using the POST /cloudapi/v6/um/users endpoint.

3. Set the following required parameters for the user: user's name, email address, and password.

4. Create a group using the POST /cloudapi/v6/um/groups endpoint.

5. Set accessAndManageDns privilege to true.

6. Assign the user to the created group using POST /cloudapi/v6/um/groups/{groupId}/users endpoint and provide the user ID in the header.

With IONOS Cloud Domain Name System (DNS), you can publish your domain names to the global DNS. The feature is built around the concept of DNS zones and records that are managed primarily through the Cloud DNS API. Along with the API operations, the Data Center Designer (DCD) provisions you with an option to grant additional users with permission to manage these DNS zones and records.

Features

The Cloud DNS offers the following key capabilities:

• High availability: The IONOS Cloud DNS infrastructure is designed with redundancy at every level, including multiple DNS servers, network links, power sources, and data centers. This redundancy ensures that if one component fails, another can take over and continue to provide service without interruption.

• Fully-managed service: The DNS infrastructure and provides the service as a SaaS model.

• Automation: The Cloud DNS API lets you automatically create, update, and delete DNS zones and records.

Concepts

• DNS: Refers to a system that converts domain names into IP addresses. The DNS translates domain names into numeric IP addresses that computers can understand and use to access websites or other internet resources.

• Name Servers: Name Servers or DNS Servers are parts of the computer's DNS infrastructure and store DNS records for a particular domain name. They provide information about the IP address or other resources associated with a domain name. When you request access to a domain, your device queries the domain's name servers to resolve the corresponding IP address.

• DNS Zone: A DNS zone is an administrative unit that contains DNS records for a specific domain. It specifies the authoritative DNS servers for that domain and their IP addresses.

• DNS Record: A DNS record is a set of instructions stored on DNS servers that maps domain names to IP addresses and vice versa. They are used to help route internet traffic, provide email services, and facilitate other internet functions. DNS records come in various formats, such as Address (A), Canonical Name (CNAME), Mail Exchange (MX), Text (TXT), and so on.

• Reverse DNS: Reverse DNS is a method of resolving an IP address to a domain name. It is the opposite of the standard DNS lookup, which resolves a domain name to an IP address. You can verify the authenticity of an IP address by checking whether the hostname associated with the IP address matches the expected domain. Reverse DNS operates through PTR (Pointer) records, which are special DNS records.

• Secondary DNS Zone: A secondary DNS zone is a read-only copy of a primary DNS zone. It holds the same DNS records for a domain and helps distribute the load and ensure redundancy. If the primary DNS server experiences issues, the secondary zone can still provide accurate DNS information, ensuring continuous availability for domain name resolution.

• DNSSEC Keys: DNSSEC keys are cryptographic keys used to enhance the security of the DNS. DNSSEC keys are generated as pairs: a private key and a corresponding public key. The private key is kept secure, while the public key is shared in DNS records. These keys are crucial for validating DNS responses, preventing tampering, and ensuring the security of DNS information.

• Time-to-live (TTL): TTL is a DNS record setting that specifies how long a DNS resolver should cache the results of a query before querying the DNS server again for updated information.

• Domain Registrar: A domain registrar is a company or an organization that manages the registration of domain names on the Internet. The Internet Corporation for Assigned Names and Numbers (ICANN) accredited registrars are responsible for ensuring the accuracy and validity of domain name registrations. Domain registrars include IONOS, Strato, Fasthosts, Arsys, Home.pl, and World4You.

Cloud DNS has a new group privilege called Access and manage DNS. The privilege must be enabled for a group so that the group members inherit this privilege through group privilege settings. Once the privilege is granted, contract users can view the Cloud DNS API.

To set user privileges to manage DNS zones and records, follow these steps:

1. In the DCD, open Management > Users & Groups under Users.

2. Select the Groups tab in the User Manager window.

3. Select the target group name from the Groups list.

4. Select the Access and manage DNS checkbox in the Privileges tab.

Revoke user privileges

You can revoke a user's Access and manage DNS privilege by removing the user from all the groups that have this privilege enabled.

To revoke this privilege from a contract administrator, disable the administrator option on the user account. On performing this action, the contract administrator gets the role of a contract user, and the privileges that were set up for the user before being an administrator will then be in effect.

Similar to creating a DNS zone, you need to provide the UUID of the DNS zone to host the new record.

To create a DNS zone of Type A, follow this step:

• Perform a POST request with these details:

  • corresponding UUID of the DNS zone,

  • name of the subdomain; example: www

  • record type; in this case: A,

  • content or destination of the A record in the form of an IPv4 address; example: 1.1.1.1

  • TTL you need (minimum 60 seconds and maximum 86.400 seconds), and

  • status of the DNS record (enable), true or false.

Request

Response

202 Successful operation

Response Fields

Create records of other types

Create records of other types Cloud DNS supports the following record types: A, AAAA , CNAME, ALIAS, MX, NS, SOA, SRV, TXT, CAA, SSHFP, TLSA, SMIMEA, DS, HTTPS, SVCB, OPENPGPKEY, CERT, URI, RP and LOC.

Here is a brief explanation of the most common record types:

• A: Specifies the IPv4 address associated with a zone name.

• AAAA: Specifies the IPv6 address associated with a zone name.

• MX: Specifies the mail exchange servers for a zone name.

• CNAME: Specifies an alias for a zone name, allowing multiple names to resolve to the same IP address.

• TXT: Allows arbitrary text to be associated with a zone name that is commonly used for SPF records and other types of verification.

• NS: Specifies the name servers for a zone name.

• SRV: Specifies the location of services for a zone name that is commonly used for Session Initiation Protocol (SIP) and other protocols.

Here you can see examples of records with different record types:

Quota

To retrieve the quota of DNS records, perform a GET request to the /quota endpoint.

Request

Response

200 OK

Response Fields

Enable DNSSEC keys for a DNS zone

To enable DNSSEC keys for a DNS zone at IONOS Cloud DNS, follow these steps:

1. Perform a POST request to the /zones/{zoneId}/keys endpoint.

2. Replace {zoneId} with the UUID of the DNS zone where you want to enable DNSSEC keys.

3. In the request body, provide the key parameters used to sign the zone. These parameters include the signing algorithm, key length for both Key Signing Keys (KSK), Zone Signing Keys (ZSK), NSEC mode (NSEC or NSEC3), and other relevant settings.

Request

Response

202 Accepted

Retrieve DNSSEC keys for a DNS zone

To retrieve DNSSEC keys for a specific DNS zone at Cloud DNS, follow these steps:

1. Perform a GET request to the /zones/{zoneId}/keys endpoint.

2. Replace {zoneId} with the UUID of the DNS zone you want to retrieve keys for.

Request

Response

200 OK

Response Fields

Disable DNSSEC Keys for a DNS zone

To disable and delete DNSSEC keys for a DNS zone at Cloud DNS, follow these steps:

1. Perform a DELETE request to the /zones/{zoneId}/keys endpoint.

2. Replace {zoneId} with the UUID of the DNS zone from which you want to remove DNSSEC keys.

Request

Response

202 Accepted

A PTR (Pointer) record is crucial for a mail server as it establishes a Reverse DNS mapping, verifying the legitimacy of the server's IP address. This record is vital for email deliverability, preventing emails from being flagged as spam during Reverse DNS checks. It contributes to forward-confirmed Reverse DNS (FCrDNS), aligning forward and Reverse DNS entries to enhance server credibility. Servers lacking a valid PTR record may face rejection by other mail servers, impacting deliverability. Overall, a PTR record is a standard best practice, promoting trustworthiness and smooth email communication. Additionally, an SPF (Sender Policy Framework) record is essential for email deliverability, as it specifies authorized mail servers for a domain, preventing email spoofing and further bolstering the authenticity of outgoing emails.

This tutorial will guide you on how to install and configure a mail server and a PTR record using IONOS . The steps we will follow are:

1. Set up a Dedicated Core server in IONOS Cloud.

2. Create an A and MX record for your mail server.

3. Install and configure mail server.

4. Add a Reverse DNS record and SPF record for your mail server.

5. Test the email deliverability.

Set up a Dedicated Core Server in IONOS Cloud

To set up a Dedicated Core server in IONOS Cloud, follow these steps:

1. Create a Dedicated Core server and configure the server in the Settings tab by following the steps in .

Dedicated Core Server network settings

2. MAC: Assigned on VM creation.

3. LAN: Select the LAN connection that is connected to the internet, by default LAN 1.

4. Firewall: By default, the firewall is disabled. To enable firewall rules, make sure that incoming and outgoing traffic is allowed on port 25 for UDP and TCP.

5. IP Management: To reserve an IP for the server, click IP Management under Management in the top menu bar.

6. Click Reserve IP and a new pop-up window Reserve IP appears. Add a Name, Number of IPs and select a region that is the same as the region of your Dedicated Core server. Click Reserve IP to reserve the IP and confirm the reservation by pressing OK.

7. Exit the IP management window and return to the Network tab of your Dedicated Core Server.

8. In the IPv4 Configuration click Add IP and a select one of your reserved IPs.

Dedicated Core Server storage settings

1. Click SSD and a new pop-up window Create New Attached Storage appears.

2. Configure the following storage details:

• Name: Enter a name that is unique within your VDC.

• Availability Zone: Leave on "Auto".

• Size in GB: Enter "50" which is sufficient for this tutorial.

• Performance: Select "Standard".

• Image: You can select one of IONOS images or snapshots, or use your own. For this tutorial, we will use an Ubuntu server image from IONOS. To make the same choice, select ubuntu-22.04-server-cloudimg-amd64 under IONOS Images.

• Password: Create a password for the "root" user of the server. You will need this password to SSH and make changes.

• SSH Keys: Select an SSH key stored in the SSH Key Manager.

• Ad-hoc SSH Key: If you have not created an SSH key, copy and paste the public part of your SSH key into this field.

• Cloud-Init user data: Leave on "No configuration".

• Boot from Device: Select this checkbox to make the SSD drive bootable.

3. Click Create SSD Storage to create the SSD storage.

Provision changes and start the Dedicated Core Server

1. Select the newly created Dedicated Core server.

2. From the Settings tab in the Inspector pane, select Power > Start.

3. Click Provision Changes in the lower right corner and further click Provision Now.

Next steps: After your changes are provisioned and the server is started, select your Dedicated Core server, click the Network tab in the Inspector pane and copy one of the IPv4 addresses.

Create an A and MX record for your mail server

Install and configure mail server

1. Connect to your Dedicated Core server via SSH:

and make sure that you are executing the following commands as root.

2. Update the system:

If a kernel is updated it is suggested that you reboot the server.

3. Install Postfix:

4. Install OpenDKIM:

5. Generate OpenDKIM keys:

Execute the following commands to generate OpenDKIM keys for your domain and move them to the appropriate directory:

6. Edit the OpenDKIM configuration file:

Add or modify the following lines:

7. Install Postfix and Mailutils:

7. Configure Postfix to use OpenDKIM:

Modify the line containing information about smtp_banner to include the domain name of your mail server, for example, mail.demo-ionos.cloud. The line should look like this:

and add the following lines at the end of the file:

and the complete /etc/postfix/main.cf file looks like this:

8. Restart services:

9. Test the configuration:

In your mailbox you should receive an email with the subject "Test Email" and the body "This is a test email" but it might be in the spam folder, depending on your email provider. In our case the email was in the spam folder with a note "Mail system could not verify that demo-ionos.cloud actually sent this message (and not a spammer)."

10. Check the mail log:

Add a Reverse DNS record and SPF record for your mail server

3. Test again the email deliverability:

To create a secondary zone on the IONOS Cloud DNS, follow this step:

• Perform a POST request to the /secondaryzones endpoint by providing the zoneName, description, and primaryIps for the IP address of the primary nameserver.

Request

Response

202 Accepted

Response Fields

Retrieve all secondary zones

To retrieve information about all the secondary zones, follow this step:

• Send a GET request to the /secondaryzones endpoint.

Request

Response

200 OK

Response Fields

Retrieve a specific secondary zone information

To retrieve information about a specific secondary zone, follow this step:

• Send a GET request to the /secondaryzones/{secondaryzoneId} endpoint.

Request

Response

Response Fields

Retrieve records for a specific secondary zone information

To retrieve records information about a specific secondary zone, follow this step:

• Send a GET request to the /secondaryzones/{secondaryzoneId}/records endpoint.

Request

Response

Response Fields

Modify secondary zone

To modify the description of a secondary zone or update the IP addresses of its primary nameserver, follow this step:

• Send a PUT request to the /secondaryzones/{secondaryzoneId} endpoint.

Request

Response

202 Accepted

Response Fields

Initiate zone transfer to a secondary zone

To initiate zone transfer from the primary zone to the secondary zone, follow this step:

• Send a PUT request to the /secondaryzones/{secondaryzoneId}/axfr endpoint.

Request

Response

200 OK

Check zone transfer status

To check zone transfer status, follow this step:

• Perform a GET request to /secondaryzones/{secondaryzoneId}/axfr endpoint.

Request

Response

200 OK

Response Fields

Delete a secondary zone

To delete a secondary zone from the IONOS Cloud DNS, follow this step:

• Send a DELETE request to the /secondaryzones/{zoneId} endpoint.

Request

Response

200 Accepted

Quota

To retrieve the quota of secondary DNS zones, perform a GET request to the /quota endpoint.

Request

Response

200 OK

Response Fields