Domains
Your application answers at its Kedalia address, shown next to its name. It can also answer under your own names, such
as hr.company.com or company.com, depending on your tier.
Add a name
In “Applications”, click “Domains” on the application's card. Type the name in “Domain name”, then click “Add”. Kedalia answers “Name added: copy its two lines into your DNS zone, then verify.”, and the name appears with the state “DNS to set”.
The name must be yours. Kedalia refuses an IP address or one of its own names: “This name is not accepted. Enter a domain you own, such as hr.company.com or company.com: not an IP address, nor a Kedalia name.”
The two DNS lines
Under the name, a table gives two lines, with their “Name”, “Type” and “Value”. Copy them into your domain's DNS zone, wherever it is managed (often at the provider that sold it to you).
- The first, of type TXT, proves the name is yours. Its name starts with
_kedalia., and its value withkedalia-verification=. - The second leads the name to your application. For a subdomain such as
hr.company.com, it is a CNAME to the application's Kedalia address. For a bare domain such ascompany.com, it is an A record to the IP address shown.
Verify
Once both lines are in place, click “Verify”. A DNS change takes time to spread: if Kedalia cannot find the first line yet, it answers “The TXT record was not found, or it does not carry the expected value.”. Check both lines, wait a few minutes, then click “Verify” again.
Once verified, the name moves to “Being set up”, and the page updates by itself. The certificate that secures connections usually arrives within a minute. The application answers on this name once it is redeployed: right away when its latest version passed its checks, otherwise at its next update. Until then, opening the name shows a “page not found”: that is normal for these few minutes. Still nothing after a quarter of an hour: click “Retry the certificate”. The name is then “Active”.
Make main
On a verified name, “Make main” makes it the name the application's e-mail links use, from its next deployment. It then carries the “Main” mark.
Sign-ins
Each name has its own sign-ins: a user signed in on one name signs in again on another. If your application signs in with Google, add each name to the authorised origins of its Google project.
Remove a name
Click “Remove” next to the name. Kedalia asks for confirmation: the application stops answering on this name. Then delete its two lines from your DNS zone: a name left pointing to Kedalia could be claimed again.