Manage zones and records
Keep the records that point clients to your services in one console. Review the name, type, destination and TTL together before publishing a change.
Connect / DNS & certificates
Connect your domain to your application.
Manage DNS zones, records and supported certificate workflows alongside your services. Track changes and verify the resulting endpoint.
- Name
- app.example.com
- Type
- A
- Destination
- 192.0.2.10 (documentation address)
- TTL
- 300 seconds (example)
- HTTPS
- Certificate configured at the endpoint
Replace the example with your domain and assigned service address.
- Naming
- Zones and DNS records
- Service identity
- Certificate operations and bindings
- Best fit
- Application domains and endpoint changes
Application architecture / DNS & certificates
Move the endpoint. Keep the name.
Prepare the destination service, review the record TTL and update the DNS value. Check authoritative resolution and the certificate presented by the endpoint before cutover.
What this gives you
A named application endpoint with a documented DNS change and certificate installation path.
Where it fits
What you can do with dns & certificates.
For teams connecting application endpoints to domain names and managing their certificate lifecycle.
Track record changes
Follow a DNS change through its operation state, then check authoritative resolution. Existing resolver caches can continue serving the previous value until its TTL expires.
Coordinate certificate operations
Use supported issuance, renewal and service-binding workflows to manage endpoint identity. Automated processing depends on the configured certificate services and CA profile.
Prepare an endpoint cutover
Plan DNS and HTTPS together when moving an application. Make the new destination ready, account for cached records and confirm the certificate served at the endpoint.
In practice
From a domain name to a working endpoint.
Use DNS to give services a stable name. Follow each record change through to resolution, then check the certificate presented by the endpoint.
Connect an application domain
Create the supported record that points the application name to its configured endpoint.
Plan for
Record type, destination, TTL and authoritative delegation.
Move an endpoint
Prepare a record change as part of a release or migration and verify resolution from outside the application network.
Plan for
Cached responses, application readiness and a rollback value.
Review service identity
Follow supported certificate operations and confirm the intended certificate at the endpoint.
Plan for
Domain validation, service binding and renewal configuration.
The workflow
From setup to everyday use.
- 01
Prepare the domain
Confirm domain ownership and the nameservers or records required for your configuration.
- 02
Publish DNS changes
Create records and check their applied state and external resolution.
- 03
Review certificates
Configure supported certificate operations and confirm installation at the endpoint.
Configuration checks
Prepare the operating environment.
- Confirm domain ownership and the authoritative nameservers in use.
- Review record names, values and TTL before submitting changes.
- Verify external DNS resolution and the certificate served by the application.
Responsibilities
Know what you maintain.
DNS & certificates / Questions
A few details before you start.
Do I need to transfer my domain registration?
Domain registration remains with your registrar. Follow the supplied verification and delegation instructions to configure the DNS workflow for your environment.
Why do clients still see the previous DNS value?
Resolvers can retain cached responses according to their TTL. Check the authoritative result and allow for caches when planning a cutover.
Is certificate issuance the last step?
Verify the certificate binding and what the live endpoint presents. Issuance alone does not confirm installation. Automated processing also requires the corresponding configured services.
Connected products