DNS in your deployment workflow
Manage domains, DNS zones, and records with Loopback. Learn how DNS, Bundles, and central permissions work together in your application deployment workflow.
Manage domains, DNS zones, and records with Loopback. Learn how DNS, Bundles, and central permissions work together in your application deployment workflow.
An application has been deployed to the cluster. For users to reach it through its domain, name resolution also needs to point to the intended target. DNS therefore belongs in deployment planning.
With Loopback, you manage domains, DNS zones, and records within your organization. You can buy domains, transfer existing domains, and connect external zones through integrations. Services such as Bundles use the zones belonging to the same organization.
Several components need to work together to make an application reachable: the domain names the service, DNS provides the associated information, and the infrastructure handles the connection.
Domains, zones, and records serve different purposes:
| Component | Purpose | Example |
|---|---|---|
| Domain | Provides the registered name | example.com |
| DNS zone | Contains the managed DNS entries | Zone for example.com |
| DNS record | Maps a name to specific information | Address for api.example.com |
| Application endpoint | Accepts the connection | Load balancer in front of the application |
For deployment planning, this means your application needs an intended endpoint and the corresponding DNS configuration alongside its target cluster.
When infrastructure changes, checking the records also belongs in the process. A successful Kubernetes rollout alone does not tell you whether the domain points to the intended target.
Loopback offers several ways to bring domains and DNS into the platform.
You can buy a domain directly through Loopback and then manage its associated zone and records. You can also transfer existing domains to Loopback.
You can connect external zones through integrations as well. Loopback supports Cloudflare and Hetzner DNS, for example. This lets you manage zones within the platform while they remain with an external DNS provider.
Your organization gains a shared management context: domains, zones, and records are maintained alongside the other services in your stack.
Loopback supports A, AAAA, TXT, CNAME, MX, and SRV records. The type you use depends on the information you want to publish under a name.
| Record type | Use |
|---|---|
| A | Maps a name to an IPv4 address |
| AAAA | Maps a name to an IPv6 address |
| CNAME | Creates an alias pointing to another DNS name |
| TXT | Stores text information, such as domain verification data |
| MX | Identifies the mail servers responsible for a domain |
| SRV | Describes a service's target and port |
A, AAAA, and CNAME records are often relevant for web applications. Your choice depends on how the intended application endpoint is addressed.
The record should reflect the actual infrastructure. If a load balancer is the entry point, the DNS configuration points to that endpoint. For users, the domain remains the familiar name of the application.
Bundles represent applications and their deployment workflows in Loopback. DNS adds the associated names and zones to this process.
Both belong to the same organization. Bundles use the zones managed there, while records and delegation are managed within the shared account.
This helps your team understand the relationship between application and domain: the Bundle describes the application's path to the cluster. DNS configuration forms part of making that application reachable.
During setup, plan both sides together:
The answers create a traceable relationship between deployment, infrastructure, and domain.
An application often runs in several environments. Clear naming helps your team distinguish them in daily work.
One possible structure looks like this:
| Environment | Example name | Purpose |
|---|---|---|
| Development | dev.example.com | Check changes during development |
| Staging | staging.example.com | Test a planned release |
| Production | app.example.com | Use the application in production |
These names form a team convention. They should fit your application structure and be understandable to everyone involved.
You then define the intended DNS target for each environment. If environments use different clusters or load balancers, the configuration needs to reflect that mapping.
This structure also makes coordination easier: developers, operations teams, and other participants can use an unambiguous name for each environment.
Existing projects often already have a domain and DNS configuration. Loopback therefore supports external zones through integrations alongside its own zones.
It helps to consider domain management and DNS zone management separately. Buying or transferring a domain concerns its registration. The DNS zone contains the entries used for name resolution.
An external DNS integration lets you manage a supported zone through Loopback. Your team can bring DNS work into the shared platform context.
Before setup, establish which integration will manage which zone. This mapping belongs in the project's technical documentation and helps with later changes.
Changing a DNS record can affect where connections to an application go. Access control therefore belongs in DNS management.
Loopback RBAC governs who may buy domains, transfer zones, and change records. You manage these permissions centrally within your organization.
When assigning permissions, consider specific tasks. People deploying application revisions may need different rights from those maintaining domains and DNS zones. Your permissions model can reflect these responsibilities.
Central management also helps you define responsibilities consistently across multiple projects.
DNS connects your applications' names to their intended targets. Domains, zones, records, and deployment endpoints therefore belong in shared technical planning.
Loopback brings DNS management together with the rest of your stack. You can buy or transfer domains, connect external zones, and manage records within your organization. Bundles use the same zones, while Loopback RBAC controls permissions.
Application reachability remains part of the same management context as your deployments.
Start with managed Kubernetes, object storage, registry, or Bundles. One account, one permission model.