Lepsto wrote the DNS records for my domain

My task manager on Lepsto now opens on its own domain, proof-ground.com, over HTTPS. I connected Cloudflare and Lepsto wrote every DNS record itself; I didn't copy one by hand.

The walkthrough above shows the whole setup, from connecting Cloudflare to opening the app on its domain. I recorded the screen in the console; Lucas, our AI avatar, narrates it.

For this flow, the domain's zone must already exist in Cloudflare. Lepsto doesn't create it or change your nameservers. If your DNS is somewhere else, Lepsto shows the records and you add them at your provider yourself.

It took three steps. First, I connected Cloudflare under Integrations, attached it to the Task manager product and approved access on Cloudflare's side. Then I added proof-ground.com in the product's Settings → Domains and switched it to Manage with Cloudflare. Finally, I added the same name to the service under Service → Networking.

The service listed the records it needed: an A record for the root, a TXT record that proves I own the name, and a CNAME for the certificate. Normally that's the moment you open your DNS provider and copy each value. Here, the records were already on the domain page, and Cloudflare showed the same records, written by Lepsto.

Lepsto checks DNS every minute, and once the records are visible, the certificate normally takes minutes. The www redirect has its own certificate, which can take tens of minutes after the root starts serving.

While DNS caught up, I added proof-ground.com as a sending domain in Mail. Its DKIM and DMARC records were written the same way. I used the root for the demo, but the Mail docs recommend a subdomain for your product's system email.

To set up your own, follow the guide to connecting a domain.