Custom Domain

By default your portal lives at <yourplatform>.netvoice.io. You can also serve it from a domain you own, such as portal.example.com. DialStack issues the TLS certificate for it and renews it automatically.

Add a Domain

1. Open your platform's page and find the Custom domain card.
2. Enter the domain and click Add domain. Use a subdomain you control, like portal.example.com. A bare domain such as example.com can't be used, because DNS doesn't allow the record it needs at the top of a domain.
3. The card lists three DNS records. Create all three with your DNS provider:
   • A CNAME that points your domain to the portal.
   • A TXT record that proves the domain is yours. Its value is unique to your platform.
   • A CNAME that lets us issue the certificate.
4. Wait. The card checks for the records on its own and marks each one when it finds it. Once all three are in place the domain goes Live, usually within minutes of the records propagating. If they aren't all found within 72 hours, the domain shows Failed.

If your domain has a CAA record, it must allow amazon.com to issue certificates, or the certificate can't be issued.

Keep the Records

Leave the DNS records in place for as long as you use the domain. The certificate is renewed automatically, and renewal relies on the certificate record. If renewal runs into trouble, the card shows a warning well before the certificate expires.

Signing In

Your users sign in on your domain the same way they do on <yourplatform>.netvoice.io. Once your domain is live, invitation and password reset emails send people to it.

Sessions don't carry over between the two addresses: someone signed in on <yourplatform>.netvoice.io signs in again the first time they visit your domain. The netvoice.io address keeps working.

Email From Your Domain

Notification emails (voicemail, fax, emergency call alerts and webhook warnings) come from noreply@<yourplatform>.netvoice.io by default. Once your domain is live, they can come from noreply@portal.example.com instead. This step is optional and doesn't affect the portal.

1. After the domain goes Live, click Send email from this domain in the Email from your domain section of the card. The section then lists three more CNAME records. They let receiving mail servers verify, through DKIM, that the emails really come from your domain.
2. Create all three with your DNS provider within 72 hours. Once they're found, the section shows Sending from your domain, and notification emails switch to your domain.

Until the records are verified, emails keep coming from the default address, so nothing goes missing in the meantime. If you later remove the records, emails go back to the default address once they are no longer found.

If the records aren't found within 72 hours, the section shows Not sending and the records stop working. Click Generate new records and create the new set in place of the old one.

Because the emails are signed for your domain, they pass DMARC checks even if your domain has a strict DMARC policy. Invitation and password reset emails still come from the default sign-in address.

Remove a Domain

Click Remove domain on the card. The domain stops serving your portal within a few minutes, and anyone using it needs to switch to another address. Notification emails go back to the default address. You can then delete the DNS records.

If the domain shows Failed, for example because the records weren't created in time, click Remove and start over and add it again.

A domain that another platform already serves can't be added. If another platform has only started adding it, that doesn't stop you: the domain goes live for whichever platform's TXT record is published.

A platform can add up to five domains a day, counting ones it removed. Past that, adding a domain is refused until the next day.