Custom Domains

On Lediv Pro a published site can also answer at a custom domain, like example.com or www.example.com. It takes one DNS record.

Connect a domain

1. In the Publish panel, click Connect a domain, or Add another domain if the site already has one.
2. Type the domain and click Connect.
3. At your DNS provider, add a CNAME on the domain itself pointing at sites.lediv.site. For a domain with no www in front, see Your apex domain.
4. Come back and click the refresh icon next to the domain.

Every value in the panel has a copy button. The certificate is issued and renewed for you, which usually takes a few minutes once the DNS is right. The panel names the step it is waiting on and what to do next.

Watch the Name field. Most DNS providers add your domain to whatever you type there, so typing www.example.com inside the zone example.com creates www.example.com.example.com and nothing works. Type only the part in front of your domain (www), or @ when there is none, then check the record your provider shows afterwards.

A site can hold several domains, and one of them is the main address, marked with the star. It serves the site and the others redirect to it keeping the path and the query, which is what puts example.com and www.example.com on one address instead of two copies of the same pages. Any live domain can become the main one. Your lediv.site address keeps working as a backup, and search engines are told to ignore it so your own domain is the one that gets indexed.

Your apex domain

The DNS standard does not allow a CNAME at the apex, your domain with nothing in front of it like example.com, and that record is how a domain reaches us, so whether it can be connected depends on who runs its DNS. Two setups make it work:

1. DNS on Cloudflare. Cloudflare flattens a CNAME at the apex, so the record works. Moving DNS there is free and you keep your registrar. Serve the record as DNS only, because proxied puts your zone in front of ours and its caching rules then apply to your site first.
2. A provider with ALIAS or ANAME (Namecheap, Porkbun, DNSimple, Route 53, among others). Point it at sites.lediv.site exactly as you would a CNAME.

If your provider does neither, the apex can only be connected by moving its DNS to one of them.

Without moving the DNS, the closest you can get is to connect www.example.com and have your registrar redirect example.com to it. Ask for permanent forwarding rather than masking, which hides your site from search engines. Leave the apex domain out of the panel.

A domain sitting behind another CDN cannot be connected, because the certificate check needs to read your DNS directly.

If another account had your domain

A domain another Lediv account holds is never handed over on request. The proof is a TXT record the panel gives you, which only whoever controls the domain's DNS can publish, and the panel says what to do with it. That is how you take a domain back from an account you no longer use, an old agency or a team you left, without their cooperation and without writing to us. A domain that is serving moves without ever going offline.

If a domain stops working

Its DNS changed. The domain stops serving and the panel shows DNS moved away. Nothing is deleted. Point the record back at sites.lediv.site, click the refresh icon, and it reconnects. Your site keeps serving at its other addresses meanwhile.

The site was taken offline. A site that breaks the acceptable use policy stops serving at every address, and your domains stop with it but stay connected. Disconnecting them is still allowed, so you can point them elsewhere while you sort it out.

You disconnected it. It stops serving straight away and the site carries on at its other addresses. This is not like releasing a lediv.site address. Nobody can connect a domain you have had live without publishing the TXT record first, and you can reconnect it yourself at any time. That protects the window you cannot see, when your CNAME may still point at us for days. Remove or repoint that record when you are done with the domain for good.

Your plan lapsed. Connected domains keep serving for 30 days, with the panel counting down and an email a week before the deadline. After that the domain stops serving but stays yours, paused rather than deleted, and nobody else can take it without proving at their own DNS that it is theirs. Go Pro again, click Bring this domain back, and it serves again within minutes. You do not touch your DNS, because the record you added is still correct.

Next steps