From 2.2.1 you can serve your organisation under a domain you own, for example iot.example.com, without handling a certificate yourself. Once the domain is verified and points to Hermetry, the platform obtains a certificate for it, checks every day that it is served, and renews it a few days before it expires.
It lives under Domains in the Organisation part of the menu. Admins can view it; adding and deleting a custom domain needs the Owner role.
- Add Domain and enter the full subdomain.
- At your DNS provider, create the CNAME the page shows and the DNS challenge record (a TXT record by default).
- Open the domain and select Verify DNS.
- Wait a few minutes, then Force SSL check. Without it the domain starts serving at the next periodic check, which can take some hours.
Use a subdomain. Most DNS providers can’t put a CNAME on a bare domain.
Your free address under the platform domain keeps working whatever happens to the custom one, and it can’t be removed. Keep it bookmarked: if a DNS change goes wrong, that is how you get back in. Owners and admins are told when a certificate is about to expire and its renewal failed.
Whether you have custom domains, and how many, depends on the plan. The Domains page tells you which applies.
One of our clients has DNS with a provider that only adds TXT records through a support ticket, which takes days. Is there a way around the TXT challenge?
Yes. An administrator can switch new domains to a CNAME challenge in the domain settings (Preferred DNS Challenge: TXT record or CNAME record). That setting exists for exactly this kind of DNS service.
That also matters because a pending challenge is valid for 24 hours. After that you verify again and get a new one, so a TXT record that takes days to go in would always arrive too late.
What happens to links in notification e-mails if the custom domain stops serving? Do people get a dead link?
No. One domain is marked Primary. E-mail and notification links use the primary domain while it serves, and the free address otherwise.
Set one up for a customer portal on Friday. Verify DNS went through on the first try and Force SSL check showed SSL Active roughly ten minutes later. The Timeline tab on the domain was useful to show the customer what happened when, they like that sort of thing.
- You must be logged in to reply to this topic.
Join the conversation
Sign in to ask and answer, like helpful posts and mark the reply that solved your problem. Every contribution earns points and levels.