How to connect your domain to Sydnee

Connect a domain or subdomain to give your client portal a branded web address, such as portal.yourfirm.com.

This article explains how to connect the domain, verify ownership when required, and configure its Domain Name System (DNS) records.

You must be a Sydnee owner or admin to configure a custom domain.

Before continuing, confirm that:

We recommend using a subdomain for your client portal:

If your root domain already hosts your public website, use a subdomain. Changing the root domain’s A record may affect that website.

Enter the complete domain or subdomain you want clients to use.

Enter the hostname without a protocol or path.
​

Use:

Do not use:

Sydnee checks the format before allowing you to continue.
​

Some domains require an additional ownership check before they can connect to Sydnee.
​

If you see Verify domain ownership, Sydnee will display a TXT record with three fields:

Add this record through the company that manages your DNS.

Your DNS provider may call the Name field “Host” or “Hostname.”
​

DNS changes are not always visible immediately. If Sydnee cannot find the record, wait a few minutes and try again. You do not need to restart the setup.
​

After ownership verification, Sydnee checks whether the domain points to the correct destination.
​

If you see DNS Configuration Needed, add the record displayed in Sydnee. Always use the current value shown on the Domain settings page.
​

A subdomain is an address such as portal.yourfirm.com.

Sydnee will normally ask you to create a CNAME record:

Do not copy a CNAME value from this article. Sydnee displays the correct value for your domain.
​

A root domain is an address such as yourfirm.com.

Sydnee will normally ask you to create an A record:

Some DNS providers leave the Name field blank instead of using @. Check your provider’s instructions if it does not accept @.
​

DNS changes can take up to 24 hours to propagate.
​

Sydnee checks the configuration while you are on the Domain settings page. You can also select Refresh to check again.
​

When the domain is ready, the page will display Setup successful.
​

Open the domain in a new browser tab to confirm that your client portal loads correctly before sharing the address with clients.
​

Sydnee automatically provisions a Secure Sockets Layer (SSL) certificate after the domain connects.
​

You do not need to purchase or upload a certificate. The certificate allows clients to open the portal securely over https://.
​

If Cloudflare manages your DNS, set the Sydnee routing record to DNS only.

In Cloudflare:

Cloudflare’s proxy can prevent Sydnee from confirming the domain configuration.
​

Confirm that:

Wait a few minutes, then select Verify TXT record again.
​

Compare the A or CNAME record with the current values shown in Sydnee.
​

Check for older records using the same name. An existing record may conflict with the new configuration.
​

If you use Cloudflare, confirm that the record is set to DNS only.
​

A domain can only belong to one Sydnee account at a time.
​

If another Sydnee account uses the domain, remove it from that account before continuing.
​

If another hosting project uses the domain, use an unused subdomain or coordinate the domain transfer before reconnecting it.
​

DNS changes can reach different networks at different times.

Wait for propagation to finish, then try:

You can disconnect the custom domain and return to your Sydnee subdomain.

If verification is still pending, select Remove domain to cancel the setup.
​

Use a subdomain if your root domain already hosts your public website.

For example, connect portal.yourfirm.com while keeping yourfirm.com connected to your existing website.
​

DNS changes can take up to 24 hours to propagate. Sydnee will show Setup successful when it detects the correct configuration.
​

No. Sydnee provisions the SSL certificate after the domain connects.
​

Yes. Remove the current domain from Company Settings → Domain, then connect the new domain.
​

The domain remains pending. Check the TXT record, wait for the DNS change to propagate, and select Verify TXT record again.