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:
In the DCD, open Management > Users & Groups under Users.
Select the Groups tab in the User Manager window.
Select the target group name from the Groups list.
Select the Access and manage DNS checkbox in the Privileges tab.
Set Access and manage DNS privilege
Result: The Access and manage DNS privilege is granted to all the members in the selected group.
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.
Warning: You can disable the Access and manage DNS privilege from every respective group the user belongs to. In this case, all the members in the respective groups would also be revoked from this privilege.
To revoke this privilege from a contract administrator, disable the administrator option on the user account. On performing this action, the contract administrator falls back into the role of a contract user. All the privileges that were set up for the user before being an administrator will then be in effect.
Overview
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.
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.
DCD How-Tos
By default, the Cloud DNS records and zones can be managed using the that are accessible only by contract owners and administrators.
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 .
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:
You can import a DNS zone from your existing DNS provider to IONOS Cloud.
Prerequisite: You need an IONOS Cloud account with API credentials configured with the appropriate permissions.
To import an existing zone to IONOS Cloud DNS, follow these steps:
Create a DNS zone without records.
Perform a PUT request providing the zoneId of the newly created zone and the zone file.
Result: On a successful PUT request, the records provided in the zone file will be added to your DNS zone.
Important: If the zone file you import contains CNAME entries that point to names in another private zone, Azure DNS resolution of the CNAME will fail unless the other private zone is imported or the CNAME entries are modified.
Request
curl--location--requestPUT'https://dns.de-fra.ionos.com/zones/42b21ce3-6fc7-44af-b0c9-2aaadbf2b333/zonefile' \--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJraWQiO' \--data-raw '$ORIGIN example.com.www 60 IN A 1.2.3.4shop 60 IN CNAME app.example.com.'
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.
API How-Tos
The Cloud DNS API lets you manage DNS zones and records programmatically using conventional HTTP requests.
Prerequisite: To start using the Cloud DNS API, you need a domain name. If you do not have one already, get a domain name and register it with a domain registrar.
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.
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:
Prerequisite: You need a domain name. If you do not have one already, get a domain name and register it with a domain registrar.
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:
Save the four nameservers Cloud DNS provided upon creating the DNS zone.
Go to your Domain Registrar and update your domain's nameservers with the four nameservers from the previous step.
Note: Changes to nameservers can take up to 48 hours, but they usually happen much faster.
Result: The domain nameserver is connected to the Cloud DNS.
Set User Privileges via the API
Prerequisite: You need administrative privileges to create and assign user privileges by using the Cloud API.
To set user privileges using the Cloud API for managing DNS zones and records, follow these steps:
Authenticate to the Cloud API using your API credentials.
Create a user using the POST /cloudapi/v6/um/users endpoint.
Set the following required parameters for the user: user's name, email address, and password.
Create a group using the POST /cloudapi/v6/um/groups endpoint.
Set "accessAndManageDns" privilege to true.
Assign the user to the created group using POST /cloudapi/v6/um/groups/{groupId}/users endpoint and provide the user ID in the header.
Result: The Access and Manage DNS privilege is granted to the user.
ExternalDNS for Managed Kubernetes
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
Prerequisites: Ensure that you have the following before you begin:
A domain name that is registered with your domain provider aka Registrar or a subdomain under your control.
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 featureimage:registry:ghcr.iorepository:ionos-cloud/external-dns-plugin-providertag: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 pluginprovider:plugin# url of the provider which the external-dns will targetextraArgs:plugin-provider-url:http://localhost:8888# plugin is deployed as sidecarsidecars:-name:ionos-pluginimage:ghcr.io/ionos-cloud/external-dns-ionos-plugin:latestports:-containerPort:8888name:httplivenessProbe:httpGet:path:/healthport:httpinitialDelaySeconds:10timeoutSeconds:5readinessProbe:httpGet:path:/healthport:httpinitialDelaySeconds:10timeoutSeconds:5env:# Set port of plugin (value needs to match the container port and plugin provider url port, default value: 8888)-name:SERVER_PORTvalue:"8888"# Listen on all interfaces for kubernetes probes-name:SERVER_HOSTvalue:""# Limit possible target zones by a domain suffix (optional)-name:DOMAIN_FILTERvalue:"example1.com,example2.com"# Exclude subdomains (optional)-name:EXCLUDE_DOMAIN_FILTERvalue:"example3.com"# Limit possible domains and target zones by a Regex filter. Overrides domain-filter (optional)-name:REGEXP_DOMAIN_FILTERvalue:".*.example4.com"# Regex filter that excludes domains and target zones matched by regex-domain-filter (optional)-name:REGEXP_DOMAIN_FILTER_EXCLUSIONvalue:".*.example5.com"# When enabled, prints DNS record changes rather than actually performing them (default: false)-name:DRY_RUNvalue:"true"# Token for DNSaaS rest API authentication (mandatory) -name:IONOS_API_KEYvalue:"21215454"-name:LOG_LEVELvalue:debug# When enabled debug logs for the DNSaaS rest API are enabled (default: false) -name:IONOS_DEBUGvalue:"true"
Install ExternalDNS: To install ExternalDNS with Bitnami Helm chart, use the following commad:
Deploy application: Follow this step to deploy an application:
Deploy an echo server application by using the file echoserver_app.yaml.
apiVersion:apps/v1kind:Deploymentmetadata:name:echoservernamespace:echoserverspec:replicas:1selector:matchLabels:app:echoservertemplate:metadata:labels:app:echoserverspec:containers:-image:ealen/echo-server:latestimagePullPolicy:IfNotPresentname:echoserverports:-containerPort:80env:-name:PORTvalue:"80"---apiVersion:v1kind:Servicemetadata:name:echoservernamespace:echoserverspec:ports:-port:80targetPort:80protocol:TCPtype:ClusterIPselector:app:echoserver---apiVersion:networking.k8s.io/v1kind:Ingressmetadata:name:echoservernamespace:echoserverannotations:kubernetes.io/ingress.class:nginxspec:rules:-host:app.example1.com#This is your subdomain / record namehttp:paths:-path:/pathType:Prefixbackend:service:name:echoserverport: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:
kubectlapply-fechoserver_app.yaml
Result: The deployment of ExternalDNS on Managed Kubernetes is complete.
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-Iapp.example1.com/?echo_code=404-300
Expected result:
HTTP/1.1404NotFoundHTTP/1.1300MultipleChoices
Check DNS records
Check that the new A and TXT records are created by using the following command:
Note: Only contract administrators, owners, and users with "accessAndManageDns" privilege can create and manage DNS zones and DNS records via API. You can also set User privileges in the DCD.
Prerequisite: You need an IONOS Cloud account with API credentials configured with the appropriate permissions.
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.
Result: On a successful POST request, you receive a response containing the DNS zone UUID, Name Servers, and the request status.
{"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
Create a DNS Record
Similar to creating a DNS zone, you need to provide the UUID of the DNS zone to host the new record.
Note: There are various record types for DNS records, and each of them has unique specifications.
Prerequisite: You need an IONOS Cloud account with API credentials configured with the appropriate permissions.
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.
Result: On a successful POST request, you receive a response with the DNS record having the UUID assigned.
Info: If you want to create a Wildcard DNS record, you need to provide “*” as the name of your DNS record to match the requests for all non-existent names under your DNS zone name.
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:
Cloud DNS
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, and enable DNSSEC keys for DNS zones.
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
Tutorials
The tutorial guides you through the commonly referred topics in the Cloud DNS such as:
ExternalDNS: Cloud DNS offers ExternalDNS integration that makes Kubernetes resources discoverable via the public DNS servers. For more information, see tutorial.
Set Up a Secondary Zone: Guides you through how to set up a primary zone in IONOS Cloud Dedicated Core server and a secondary zone with Cloud DNS. For more information, see tutorial.
Create a Secondary DNS Zone
Prerequisite: Before creating a secondary DNS zone with IONOS Cloud DNS, ensure that the primary zone is capable of establishing a zone transfer with the secondary DNS server; this means port 53 is open for TCP and UDP connections.
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.
Note: For sending DNS notify messages, Cloud DNS uses following Anycast addresses: IPv4 212.227.123.25 or IPv6 2001:8d8:fe:53::5cd:25.
Result: On a successful POST request, you receive a response containing the secondary DNS zone UUID, Name Servers, primaryIps, and the request status.
Request
Response
202 Accepted
Retrieve all secondary zones
To retrieve information about all the secondary zones, follow this step:
Send a GET request to the /secondaryzones endpoint.
Result: On a successful GET request, you receive a response containing all secondary DNS zones.
Request
Response
200 OK
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.
Result: On a successful GET request, you receive a response containing the secondary DNS zone UUID, Name Servers, primaryIps, and secondary zone status.
Request
Response
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.
Result: On a successful GET request, you receive a response containing the secondary DNS zone records information: status,content, type, priority, TTL and name.
Request
Response
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.
Result: On a successful PUT request, you receive a response containing the secondary DNS zone metadata with the new updated properties.
Request
Response
202 Accepted
Initiate zone transfer to a secondary zone
Note: The creation of a secondary zone initiates zone transfer. In case of disrupted network connectivity at this time, you can initiate the zone transfer manually between the primary and secondary (i.e. secondary name server could not access primary nameserver on port 53) zones.
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.
Note: For sending DNS notify messages, Cloud DNS uses following Anycast addresses: IPv4 212.227.123.25 or IPv6 2001:8d8:fe:53::5cd:25.
Result: On a successful PUT request, you receive an HTTP response 200 OK.
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.
Result: On a successful GET request, you receive a response for AXFR communication status for each of primaryIps.
Request
Response
200 OK
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.
Result: On a successful DELETE request, you receive an HTTP status 200 Accepted.
Request
Response
200 Accepted
Set Up a Secondary Zone
This tutorial explains how to set up a secondary DNS zone in IONOS Cloud by running a bind9 server on an Ubuntu operating system. The setup includes the following configuration steps:
Set up a Dedicated Core server in IONOS Cloud.
Configure a primary nameserver on a in IONOS Cloud running a bind9 server on an Ubuntu operating system.
Create a secondary DNS zone using IONOS Cloud DNS API.
Establish and verify the zone transfer between primary and secondary zones.
Set up a Dedicated Core Server in IONOS Cloud
Note:
The user who creates the server has full root or administrator access rights. A server, once provisioned, retains all its settings (resources, drive allocation, password, and so on), even after server restart at the operating system level.
The server will only be removed from your virtual data center once you delete it in the DCD.
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 .
Result: A Dedicated Core Server is set up and started along with the configuration of Settings, Network, and Storage setup.
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 53 for UDP and TCP.
5. IPv4 Configuration: Leave to default values.
Result: The Network settings for a Dedicated Core server are configured.
Dedicated Core Server storage settings
Warning: The storage type cannot be changed after provisioning.
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 "30" 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.
Result: The Storage settings for a Dedicated Core server are configured.
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.
Result: The Dedicated Core server is provisioned and started.
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 the IPv4 address.
Configure a Dedicated Core Server as a primary nameserver
Prerequisite: A Dedicated Core server in IONOS Cloud needs to be set up and you must have the IPv4 address of the server.
To configure a Dedicated Core server and enable it to act as the primary nameserver, follow these steps:
1. SSH into the newly created Dedicated Core server.
2. Connect to the newly created server via SSH.
3. Proceed with configuring bind9 and your primary DNS zone.
4. Configure notify to the IONOS Cloud DNS anycast nameserver and allow zone update from localhost.
Note: For sending DNS notify messages, Cloud DNS uses the following Anycast addresses: IPv4 212.227.123.25 or IPv6 2001:8d8:fe:53::5cd:25.
5. Create your primary zone.
6. Edit the zone file.
7. Save your changes and quit the Vim editor.
8. Check the configuration, reload bind, and verify that the configured zone is working.
Result: The Dedicated Core server is configured as the primary nameserver in IONOS Cloud running a bind9 server on an Ubuntu operating system.
Create a secondary zone in IONOS Cloud DNS
Prerequisite: A Dedicated Core server in IONOS Cloud is set up as a primary nameserver.
To create a secondary zone in the IONOS Cloud DNS by using the REST API, follow this step:
Send a POST request to the /secondaryzones endpoint.
Response
Result: A secondary zone in IONOS Cloud DNS is successfully created By using a POST request.
Verify zone transfer
On the primary nameserver, you can verify the zone transfer in the logs by executing the following command:
You can also verify zone transfer status using IONOS Cloud DNS API:
Response
On success response: 200 OK
Result: The zone transfer between primary and secondary zones is successfully verified.
Add a record
To add a record, follow these steps:
1. On the primary nameserver, update the zone with a new record setting—A record to a TEST-NET-3 IP address:
2. Resolve the new record locally.
3. View the logs which show that a notification is sent to the secondary zone for the new record.
4. Using Cloud DNS API, verify that the newly added record is transferred to the secondary zone.
5. Globally resolve a new record from the IONOS Cloud DNS anycast network by using the following command:
Result: A record is successfully added to the primary nameserver.
Manage DNSSEC Signing Keys
Prerequisite: To sign a zone, you need to first .
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.
Result: The DNSSEC keys for a DNS zone are successfully enabled.
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.
Result: The API response contains a list of DNSSEC keys associated with the specified DNS zone.
Request
Response
200 OK
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.
Result: The DNSSEC keys for the selected DNS zone are successfully disabled. The associated DNSSEC key records for the DNS zone is removed.
Request
Response
202 Accepted
Field
Type
Description
Example
Field
Type
Description
Example
Record Type
Record Name
Record Value
Notes
2. Configure the server Network settings by following the steps in the .
3. Configure the server Storage settings by following the steps in the .
4. Continue to provision the changes and start the Dedicated Core Server by following the steps in the .
In the > Inspector pane on the right, configure the following network details in the Network tab.
1. Name: Choose a name unique to this .
In the > Inspector pane on the right, configure the following storage details in the Storage tab.
curl--location'https://dns.de-fra.ionos.com/secondaryzones' \--header 'Content-Type: application/json' \--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJraWQiO' \--data '{ "properties": { "zoneName": "example.com", "description": "This is a secondary zone created in IONOS Cloud DNS", "primaryIps": [ "1.2.3.4", "5.6.7.8" ] }}'
{"id":"a1bc82de-4cc5-40ca-bfb3-4e93bd9a367c","type":"secondaryzone","href":"/secondaryzones/a1bc82de-4cc5-40ca-bfb3-4e93bd9a367c","metadata":{"createdDate":"2023-08-04T10:21:32+00:00","lastModifiedDate":"2023-08-04T10:21:33+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ],"state":"AVAILABLE" },"properties":{"description":"This is a secondary zone created in IONOS Cloud DNS","primaryIps": ["1.2.3.4","5.6.7.8" ],"zoneName":"example.com" }}
{"id":"0a85684c-2171-5a78-985a-a3999a0f5046","type":"collection","href":"/secondaryzones?limit=100&offset=0","items": [ {"id":"a1bc82de-4cc5-40ca-bfb3-4e93bd9a367c","type":"secondaryzone","href":"/secondaryzones/a1bc82de-4cc5-40ca-bfb3-4e93bd9a367c","metadata":{"createdDate":"2023-08-04T13:14:28+00:00","lastModifiedDate":"2023-08-04T13:14:28+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ],"state":"AVAILABLE" },"properties":{"description":"This is a secondary zone created in IONOS Cloud DNS","primaryIps": ["1.2.3.4","5.6.7.8" ],"zoneName":"example.com" } }, {"id":"33085c93-425c-4909-9a5c-64ebf34dd9e9","type":"secondaryzone","href":"/secondaryzones/33085c93-425c-4909-9a5c-64ebf34dd9e9","metadata":{"createdDate":"2023-08-04T13:15:32+00:00","lastModifiedDate":"2023-08-04T13:15:32+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ],"state":"AVAILABLE" },"properties":{"description":"This is a secondary zone created in IONOS Cloud DNS","primaryIps": ["1.2.3.4","5.6.7.8" ],"zoneName":"example.info" } }, {"id":"fa4e179a-b1ab-4de5-ae38-48d5f02a605f","type":"secondaryzone","href":"/secondaryzones/fa4e179a-b1ab-4de5-ae38-48d5f02a605f","metadata":{"createdDate":"2023-08-04T13:15:40+00:00","lastModifiedDate":"2023-08-04T13:15:40+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ], "state":"AVAILABLE" },"properties":{"description":"This is a secondary zone created in IONOS Cloud DNS","primaryIps": ["1.2.3.4","5.6.7.8" ],"zoneName":"example.net" } }, {"id":"04706207-a691-4710-902d-10acf5441bf1","type":"secondaryzone","href":"/secondaryzones/04706207-a691-4710-902d-10acf5441bf1","metadata":{"createdDate":"2023-08-04T13:15:46+00:00","lastModifiedDate":"2023-08-04T13:15:46+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ], "state":"AVAILABLE" },"properties":{"description":"This is a secondary zone created in IONOS Cloud DNS","primaryIps": ["1.2.3.4","5.6.7.8" ],"zoneName":"example.org" } } ],"offset":0,"limit":100,"_links":{"self":"/secondaryzones?limit=100&offset=0","next":"/secondaryzones?limit=100&offset=100" }}
{"id":"04706207-a691-4710-902d-10acf5441bf1","type":"secondaryzone","href":"/secondaryzones/04706207-a691-4710-902d-10acf5441bf1","metadata":{"createdDate":"2023-08-04T13:15:46+00:00","lastModifiedDate":"2023-08-04T13:15:46+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ],"state":"AVAILABLE" },"properties":{"description":"This is a secondary zone created in IONOS Cloud DNS","primaryIps": ["1.2.3.4","5.6.7.8" ],"zoneName":"example.org" }}
curl--location--requestPUT'https://dns.de-fra.ionos.com/secondaryzones/04706207-a691-4710-902d-10acf5441bf1' \--header 'Content-Type: application/json' \--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJraWQiO' \--data '{ "properties": { "zoneName": "example.org", "description": "Changing description and primaryIps for secondary zone example.org", "primaryIps": [ "5.6.8.7", "12.23.34.99" ] }}'
{"id":"a1bc82de-4cc5-40ca-bfb3-4e93bd9a367c","type":"secondaryzone","href":"/secondaryzones/a1bc82de-4cc5-40ca-bfb3-4e93bd9a367c","metadata":{"createdDate":"2023-08-04T10:21:32+00:00","lastModifiedDate":"2023-08-10T09:32:29+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ],"state":"AVAILABLE" },"properties":{"description":"Changing description and primaryIps for secondary zone example.com","primaryIps": ["5.6.8.7","12.23.34.99" ],"zoneName":"example.com" }}
curl--location'https://dns.de-fra.ionos.com/secondaryzones' \--header 'Content-Type: application/json' \--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJraWQiO' \--data '{ "properties": { "zoneName": "primary-zone.de", "description": "This is a secondary zone for primary-zone.de in IONOS Cloud DNS", "primaryIps": [ "<IP-ADDRESS>" ] }}'
{"id":"bdae7da0-0363-49d7-929d-92992786efe1","type":"secondaryzone","href":"/secondaryzones/bdae7da0-0363-49d7-929d-92992786efe1","metadata":{"createdDate":"2023-08-06T19:36:58+00:00","lastModifiedDate":"2023-08-06T19:36:59+00:00","nameservers": ["nscs-ic.ui-dns.com","nscs-ic.ui-dns.de","nscs-ic.ui-dns.org","nscs-ic.ui-dns.biz" ],"state":"AVAILABLE" },"properties":{"description":"This is a secondary zone for test-dns-public.info in IONOS Cloud DNS","primaryIps": ["<IP-ADDRESS>" ],"zoneName":"test-dns-public.info" }}
root@ubuntu:~#journalctl--unitnamed--followAug 07 14:43:39 ubuntu named[2666]: client @0x7f467825b958 212.227.123.26#33308 (primary-zone.de): transfer of 'primary-zone.de/IN': AXFR started (serial 2017060104)
Aug 07 14:43:39 ubuntu named[2666]: client @0x7f467825b958 212.227.123.26#33308 (primary-zone.de): transfer of 'primary-zone.de/IN': AXFR ended: 1 messages, 8 records, 299 bytes, 0.001 secs (299000 bytes/sec) (serial 2017060104)
root@ubuntu:~#dig+shortwww.primary-zone.de@ns.ui-global-dns.com217.160.0.148root@ubuntu:~#nsupdate> server 127.0.0.1> zone primary-zone.de> update add www2.primary-zone.de. 600 IN A 203.0.113.1> send> quit
Aug 07 16:00:22 ubuntu named[2666]: client @0x7f467000d0a8 127.0.0.1#34056: updating zone 'primary-zone.de/IN': adding an RR at 'www2.primary-zone.de' A 203.0.113.1
Aug0716:00:22ubuntunamed[2666]:zoneprimary-zone.de/IN:sendingnotifies (serial 2017060105)
