Use Cases

Scenario 1: Automating Infrastructure Roll-Out with Terraform and IONOS Cloud DNS

Precondition

As a developer using IONOS Cloud to host your application, you want to automate the entire infrastructure deployment process, including configuring DNS records.

Solution

To automate the infrastructure deployment, including DNS records, ensure that you install Terraform on your local machine or CI/CD environment. It streamlines the provisioning process, improves consistency, and reduces manual configuration errors.

Next, configure the IONOS Provider in Terraform, including your authentication credentials; define infrastructure resources for your application, such as virtual servers, networks, and load balancers; configure DNS records for your application; and initialize and apply the Terraform configuration to create the infrastructure.

Terraform provisions the defined resources and sets up the DNS records accordingly. It eliminates the operational overhead and security considerations that control DNS resources residing with a central team. You can also move away from manual, error-prone changes to automation with all its benefits.

IONOS Cloud ensures that the DNS records correctly resolve to the server's IP address and that the application is accessible through the browser. A consistent approach to change management also makes rolling back to previous states easy.

By following these steps, you can manage your infrastructure as code, ensuring reproducibility and easier maintenance of resources consistently and efficiently. The integration with IONOS Cloud DNS allows the dynamic configuration of DNS records to match the infrastructure deployment, minimizing downtime and reducing manual configuration tasks.

Scenario 2: Automatic DNS Record Updates with ExternalDNS for Managed Kubernetes with Ingress and Reverse DNS

Precondition

Imagine you have a web application hosted on a Managed Kubernetes (K8s) cluster provided by IONOS, which also offers Managed Kubernetes and DNS services. Your application is accessible via Ingress, but the service's IP address is dynamic. You want the domain to automatically point to the current IP address and ensure that Reverse DNS is properly configured.

Solution

To enable automatic DNS record updates for a dynamic IP address in a Managed Kubernetes environment while using Ingress and ensure that the application remains accessible at its domain name, you need to deploy the application within the Kubernetes cluster and provision the cluster with the necessary resources.

Following provisioning, deploying an Ingress Controller, and setting up and configuring cloud DNS is crucial. IONOS, the DNS provider, processes the cloud DNS settings, allowing for better reputation and accessibility of the web application.

You can test the deployment by modifying the Ingress resource to verify that ExternalDNS updates the corresponding DNS records correctly. For example, upon changing the service or a host. ExternalDNS automatically updates the DNS record whenever the Ingress resource changes, ensuring the application remains accessible via its domain name without manual intervention.

IONOS Cloud is compatible with any Kubernetes deployment. This compatibility ensures your application users have a seamless experience with minimal disruptions or manual interventions.

By leveraging Ingress and Cloud DNS capabilities, you can ensure that your application remains consistently accessible under its domain name, providing a smooth experience for end users while reducing administrative overhead. For more information, see ExternalDNS for Managed Kubernetes.