The four record types in plain language
This guide summarises official connect-domain docs from Carrd, Framer and systeme.io and Cloudflare's DNS reference, read on 30 October 2026. Always copy the exact values your own dashboard shows; some vendors generate them per site.
| Record | What it does | Who usually needs it |
|---|---|---|
| A | Maps a name to an IPv4 address [9] | Your website builder, for the bare domain |
| AAAA | Same as A but for IPv6 addresses [9] | Often nobody; Carrd and Framer say to remove them for @ [3][5] |
| CNAME | Maps one name to another canonical name [9] | Your builder for www or a subdomain; systeme.io for email authentication |
| TXT | Stores text in DNS, often to prove you own a domain [9] | Email authentication, search console and other verification |
| MX | Required to deliver email to a mail server [9] | Your email provider only |
A records: pointing the bare domain
Framer's IPs are anycast addresses, so the same two numbers work worldwide. Carrd does not publish its IP in the docs; it shows it in the Publish dialog when you enter your domain. [4][1]
| Builder | Host | Value | Notes |
|---|---|---|---|
| Carrd | @ | The target IP shown in Carrd's Publish dialog | Requires Pro Standard or higher. Carrd's troubleshooting page says @ should have only two A records, so add exactly what the dialog lists and nothing else [1][3] |
| Framer | @ | 31.43.160.6 | Add both IPs; remove any other A or AAAA records [4] |
| Framer | @ | 31.43.161.6 | If your registrar allows only one A record, one Framer IP is acceptable [5] |
| systeme.io | No A record | Root forwards to www, or an ALIAS record on hosts like Hostinger | systeme.io connects via www CNAME [6] |
CNAME records: www, subdomains and validation
systeme.io asks for a trailing dot on values, but warns that some hosts such as Hover do not accept one; if your domain loses its Ready to use status, check that first. If your DNS host refuses a CNAME because of a conflicting record, systeme.io says to ask the host which record conflicts and whether it is safe to remove. [6]
| Builder | Host | Value | Purpose |
|---|---|---|---|
| Carrd | www | Your bare domain, such as domain.ext | Sends www to the main site [1] |
| Carrd (subdomain) | subdomain | An A record to the IP shown, not a CNAME | Carrd uses an A record for subdomains [2] |
| Framer | www | sites.framer.app | Some providers need a trailing dot [4] |
| Framer (subdomain) | your subdomain | sites.framer.app | Same target as www [4] |
| systeme.io | www | A cloudfront.net value from your popup | Points the site [6] |
| systeme.io | A long _code host | A value ending acm-validations.aws. | Validation record; copy exactly [6] |
| systeme.io (subdomain) | subdomain, plus a validation _code host | cloudfront.net and acm-validations.aws values from your popup | A subdomain can serve only one site [8] |
| systeme.io (email) | Generated host, plus systemeio1._domainkey and systemeio2._domainkey | inbound.systeme.io., key1.systeme.io., key2.systeme.io. | Email domain authentication [7] |
TXT and MX: the records to leave alone
None of the three builders' website connection docs ask you to change MX records. MX records route your email, so deleting or editing them while connecting a site is the classic way to stop receiving mail. [9]
TXT records are usually there to prove ownership to some service, such as an email provider or search console. Only add the TXT records a vendor asks for. systeme.io's email authentication adds one: a DMARC TXT record at _dmarc, using the value generated in your account. [7]
What you should remove: AAAA records on @ (Carrd says they are not needed; Framer says they can stop SSL being issued), extra A records including hidden ones, registrar parking records and registrar URL redirects (Framer handles HTTP to HTTPS itself). [3][5]
| Record you find | Action when connecting a builder | Why |
|---|---|---|
| MX | Keep | Delivers your email [9] |
| TXT you did not create today | Keep | Likely verification or email authentication |
| Old A record on @ | Replace with the builder's | Only one destination should answer for the site [5] |
| AAAA on @ | Remove (Carrd, Framer) | Not needed; can block SSL on Framer [3][5] |
| Parking record or URL forwarding | Remove (Framer) | Interferes with the connection [5] |
Worked example: a registrar DNS screen before and after
Example.com has a parked page at the registrar and email at a mail provider. The owner is moving the site to Framer. Values below use documentation placeholder addresses except the Framer records, which are Framer's published values. [4]
| Type | Host | Before | After |
|---|---|---|---|
| A | @ | 192.0.2.10 (registrar parking) | 31.43.160.6 |
| A | @ | none | 31.43.161.6 |
| AAAA | @ | 2001:db8::10 | deleted |
| CNAME | www | parking.registrar.example | sites.framer.app |
| MX | @ | mail provider's server | unchanged |
| TXT | @ | mail provider's verification text | unchanged |
Propagation, Cloudflare and checking your work
Wait times differ by vendor: Carrd says initialization can take up to an hour; Framer's connect guide says up to 48 hours and its troubleshooting guide up to 24; systeme.io says 24 to 48 hours. [1][4][5][6]
If your DNS is on Cloudflare, proxied records return Cloudflare's IP addresses instead of your builder's. Framer tells you to set Cloudflare to DNS only. Cloudflare notes MX and TXT records are always DNS only. [5][10]
systeme.io and Framer both point to dnschecker.org: enter the full record name, choose the record type and look for the builder's value worldwide. [6][5]
- Screenshot your current DNS before changing anything.
- Copy values from your builder's dashboard, not from a blog post.
- Change only A and CNAME records for the site; leave MX and existing TXT alone.
- Delete AAAA on @ and registrar parking or forwarding.
- Check with dnschecker.org, then wait the vendor's stated time before contacting support.
Questions before you decide
Will connecting my domain to a website builder break my email?
Not if you leave MX and existing TXT records alone. Carrd, Framer and systeme.io's website connection docs ask only for A and CNAME records (systeme.io adds a validation CNAME), so email records do not need to change.
Why does Framer ask for two A records?
Framer's connect guide lists two anycast IPs, 31.43.160.6 and 31.43.161.6, for the root domain. Its troubleshooting guide says that if your registrar allows only one A record, using a single Framer IP is acceptable.
Should I delete AAAA records?
For Carrd and Framer, yes for the root domain. Carrd says AAAA records for @ are not needed, and Framer says it does not support IPv6 and that AAAA records can prevent SSL certificates from being issued.
How long do DNS changes take?
Carrd says initialization can take up to an hour. Framer says up to 24 to 48 hours depending on the article, and systeme.io says 24 to 48 hours. Check with dnschecker.org before contacting support.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Carrd docs: using a custom domain Accessed 30 Oct 2026
- Carrd docs: using a custom subdomain Accessed 30 Oct 2026
- Carrd docs: sites troubleshooting Accessed 30 Oct 2026
- Framer help: how to connect a custom domain Accessed 30 Oct 2026
- Framer help: troubleshooting custom domain issues Accessed 30 Oct 2026
- systeme.io help: how to connect your domain to systeme.io Accessed 30 Oct 2026
- systeme.io help: how to authenticate your personal domain name Accessed 30 Oct 2026
- systeme.io help: integrating your subdomain Accessed 30 Oct 2026
- Cloudflare docs: DNS record types Accessed 30 Oct 2026
- Cloudflare docs: proxy status Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.