A domain's DNS at Fairpage
Fairpage can keep a domain's DNS, so the bare domain connects at any registrar, and its email, newsletter and verification records are edited on the domains page.
On this page
When to use it
Fairpage sites run on Cloudflare, which a domain reaches by name, not by
a fixed IP address, so an A record does not connect a domain. Use this
when the company the domain's DNS is at cannot point the bare domain at a
name: it takes no CNAME, ALIAS or ANAME on @. unlimited.rs,
GoDaddy, Route 53, DigitalOcean and most cPanel hosts are like this. The
domains page offers it next to a domain that is not connected. It uses one
of the site's two domains.
It also works for a domain whose DNS answers nothing, as when the DNS host has no records for it: there is nothing to copy, so add the records the domain needs, your email's MX first, before you continue.
Email and hosting stay where they are. From then on, the domain's DNS records are changed on the domains page, not at the old DNS host.
Two cases it refuses:
- A domain whose DNS is on Cloudflare already. Add the records there instead, in that Cloudflare account.
- A domain with DNSSEC on at its registrar. Changing the name servers with it on takes the domain off the internet. Turn DNSSEC off there, wait a day, then try again.
Moving the DNS here
- On Domains, under the domain: Move DNS to Fairpage. Fairpage copies the records the domain has now. Nothing changes until step 3.
- Check the copy, listed under the domain. Your mail (its MX records) and every address you use, such as shop.example.com, should be there; Missing one? Add it adds any that is not. Records found online that the copy lacks are marked Found online and are added when you continue. Then Continue. A move not continued within 2 days is called off; the page shows the date.
- At the company the domain is registered with, replace its name servers with the two the page shows. For a domain at unlimited.rs, the page lists where in its panel to change them. Replace the old ones; don't add Fairpage's beside them. The site and email keep working while the change spreads, which takes minutes to a day. You can close the page; Check now says what the name servers are now.
- Once the domain's registration points at them, Fairpage points the domain and its
www at the site, and both connect. The owners get an email for each.
Email keeps arriving where it did. If a mail app or webmail uses the
domain itself as its server, change that to
mail.and the domain.
If the site has no plan when the name servers change, the domain waits: its records keep answering as before, the owners are emailed, and it connects once a plan is chosen. If something else stops it, the page says so, and Fairpage tries again on its own.
Cancel the move stops it before then. If you changed the name servers already, set them back to the ones the page names first, or the domain and its email stop working; Fairpage refuses to cancel while the name servers point at it. A move whose name servers are not changed within 14 days ends; the owners are emailed four days before, and when it ends.
The records
The domain's records are listed by what they are for: Email, Newsletters, Verifications, Other and Website, each with what stops working without them. Fairpage's own records, which point the domain at the site, are marked Set by Fairpage and cannot be changed. Records Fairpage copied that it cannot make again (CAA and SRV) are marked Copied as it was. The others have Edit and Remove.
A change that could take the domain's mail asks for the code from your
authenticator app, if two-step sign-in is on: an MX or NS record, the
address of the name your MX points at (often mail), autodiscover
and autoconfig, and _acme-challenge records, which get a certificate
issued.
Connecting a service
- Connect a service, then choose it. The page says where in the service its records are listed. For Google Workspace, fill them in adds its mail records, which are the same for every domain; then paste its verification record. Its DKIM record shows in Google only later: connect Google Workspace again then.
- Copy the whole records table the service shows and paste it, in any
form: names as
@, blank,wwwor the full name, values with or without quotes and trailing dots, with the priority and TTL columns in any order. For a verification, paste the value alone. - Read the records shows what will be saved, what is left out and why, and any line it could not read. Save (with the number of records) adds them.
The services listed: Google Workspace, Microsoft 365, Zoho Mail, Proton Mail, iCloud Mail, Migadu and Fastmail for email; Mailchimp, Brevo, MailerLite and Klaviyo for newsletters; Google Search Console, Meta (for the pixel and ads), Pinterest and Bing for verifications. Add a record adds any other.
A domain has one SPF record. A service's SPF terms join the one there, and a record that would need more than 10 DNS lookups, the most mail servers follow, is refused. A second email service's MX records are refused too: remove the first service's, or mail is split between the two. So is a second DMARC record: the one there stays. A DKIM key pasted where the service had one replaces it.
Checking the records
The page lists what is wrong with the domain's mail records: two SPF
records, mail with no SPF record, no DMARC record or two. Gmail and Yahoo
expect a DMARC record from domains that send mail; Add a DMARC record
adds one that only reports (v=DMARC1; p=none). Check what is live
reads public DNS for each record: Live, or Not visible yet for a
record the internet does not see yet.
Undoing a change
After a change, Undo sits above the records. Recent changes, under the records, lists the last changes with who made them. Undo puts a removed record back as it was, removes an added one, or gives a changed one its value before.
Moving the DNS away
A domain whose DNS Fairpage keeps cannot be removed from the site while it does. In the ⋯ menu beside DNS at Fairpage, Download its records gives a file most DNS hosts import. Move its DNS away keeps the records answering until the domain's name servers point elsewhere, and lists them so you can copy them to the new host: set them up there first, then change the name servers. After that, the domain opens the site only if the new DNS host points it here. Until then, Keep its DNS at Fairpage takes it back. A domain whose name servers are moved away without stopping first ends too, and the owners are emailed its records.
When a site is deleted, its owners are emailed the domain's records, and Fairpage keeps answering for the domain for 30 days, or until its name servers change.
What happens when a site's plan ends: Fairpage keeps answering for the domain, so its email keeps working.
Not answered here?
A person at Fairpage replies on the request’s page, within one business day on Plus, two on Lite.
Fairpage