DNS records for your domain
A domain bought elsewhere keeps its DNS where it is: you add an ownership record and two pointers, and the platform checks each one daily.
A Domain you bought elsewhere keeps its DNS where it is. You add three DNS Records at your registrar, and the platform checks each one every day.
Records, not nameservers
You never change nameservers. Your registrar keeps answering for the name, so your existing email and any other records keep working.
To hand the name over completely, transfer it with Domain.transfer. A name you buy here needs no records at all.
The three records
Domain.connect returns the exact names and values, and the Portal shows the status of each. The shape is always the same:
| Type | Name | Value | Why |
|---|---|---|---|
TXT | @ | sb-verify= | Proves you hold the name |
CNAME | _acme-challenge | leaseline.com.validate… | Renews the certificate with no step from you |
CNAME | www | leaseline.com.edge… | Serves your Site |
The bare name, leaseline.com with no www, often cannot hold a CNAME. If your registrar refuses one, it offers an ALIAS or ANAME record; use that. If it offers neither, add the A records Domain.connect lists instead.
The rest of the business answers at paths on the same name, such as leaseline.com/ and leaseline.com/, with no more records. An alias such as api.leaseline.com needs one more CNAME, which Domain.connect lists when you ask for the alias.
How long it takes
Most registrars publish a new record within minutes, and the platform checks every few minutes until it sees them. The Domain moves from verifying to live once all three answer, and the certificate issues in the same step.
A record can take up to its old TTL to replace one that was there before, often an hour and at most two days. Wait that long before changing anything a second time.
When it does not connect
Fix my domain runs Domain.verify, which names each failing check and its fix. The usual causes, in order:
| What you see | Cause | Fix |
|---|---|---|
The record shows as missing | The registrar added your domain to the name, making www.leaseline.com.leaseline.com | Enter only www or _acme-challenge as the name |
| The site loads with a certificate warning | The _acme-challenge record is missing, or a CAA record excludes the platform's certificate authority | Add the record, or add the authority to the CAA record |
| The old site still loads | An old A or CNAME record for the same name is still there | Remove the old record |
| It works for you but not for others | Their resolver still holds the old answer | Wait out the old TTL |
The status flips between live and degraded | A proxy or firewall in front of the name answers for it | Turn the proxy off for these records |
A degraded canonical Domain opens an Incident, so the operations agent hears about it before your customers do.
Email at the same name
Mail records are separate from these three. Get email at my domain adds SPF, DKIM, DMARC and MX, and leaves any mail you already run untouched until you move it.