In this guide
Before you start
Have access to your domain registrar and the intended service endpoint. Record existing DNS values before changing them.
Step-by-step workflow
- Prepare delegation
Keep access to your registrar and confirm the authoritative DNS setup. Use the exact verification or nameserver values supplied by your environment.
- Create the record
Select the zone and record type, then supply the name, destination and TTL. Review existing records before changing a destination.
- Follow the DNS change
Inspect the change operation and authoritative resolution. Allow for previously cached answers during a cutover.
- Complete endpoint identity
For supported certificate bindings, follow validation, issuance and installation. Check the certificate actually presented by the HTTPS endpoint.
Domain ownership
Use the domain verification flow and the exact record values shown in the console. Domain registration remains with your registrar. Do not assume nameserver addresses that have not been provided for your environment.
Zones and records
Create supported DNS zones and record sets from the DNS area. Review record type, name, value and TTL before submitting changes. Check both the operation state and external DNS resolution.
DNSSEC
Where enabled, follow the DNSSEC workflow and review the delegation information required by your registrar. A DNS management interface alone does not establish signed delegation or Anycast delivery.
Certificates
The platform includes certificate workflows and service bindings. Automated processing depends on the configured controller and CA profile. Inspect operation and installation state; submitting an issuance request does not prove that the endpoint is serving the certificate.
Check your result
The intended name resolves to the configured endpoint. Where certificates are in use, the endpoint presents the intended certificate for that name.
If something does not work
Check authoritative nameservers and the applied record state if resolution differs. Cached records can persist according to their TTL. For certificate issues, inspect validation, operation and service binding separately.
- Some clients still reach the previous address
- Compare authoritative answers with the client's resolver response. Existing caches can retain a value until its TTL expires.
- A certificate is issued but HTTPS still fails
- Inspect the service binding and endpoint configuration. Confirm that automated processing is enabled where required; issuance and installation are separate steps.