Branded FQDN CNAMES
When it is not possible to delegate a domain to the HaaS Platform, each of the individual FQDNs for the brand must be set up as CNAMES to the HaaS platform space FDDNs.
tip
If Biza is issuing the certificates for the brands, then you will likely combine this with the Domain Control Validation runsheet.
Inputs
Biza will supply the CNAME records to be created by the customer.
For example:
| FQDN | CNAME |
|---|---|
| auth.holder.com.au | auth.7dkse.haas.yellow.spaces.2492.au |
| api.holder.com.au | api.7dkse.haas.yellow.spaces.2492.au |
| public.holder.com.au | public.7dkse.haas.yellow.spaces.2492.au |
| haas-manager.holder.com.au | haas-manager.7dkse.haas.yellow.spaces.2492.au |
| dashboard.holder.com.au | dashboard.7dkse.haas.yellow.spaces.2492.au |
| auth-secure.holder.com.au | auth-secure.7dkse.haas.yellow.spaces.2492.au |
Tasks
Create the appropriate CNAME records in the customer's DNS zone.
Outputs
- The CNAME records are created in the customer's DNS zone and mapping to the space canonical space names for the FQDNs.