DNS & Go-Live Instructions

Everything you need to point your domain at FatLab and take your website live.

When your new site is ready to launch, the final step is updating your domain's DNS so visitors are routed to our servers. The records below are all you need. The quick reference at the top is for developers, and the plain-English walkthrough further down is for everyone else. If you would rather we handle the switch for you, we can do that too.

On This Page

DNS Records at a Glance

For developers and DNS administrators. All records are set on the base / apex domain and are shown in {host} -> {value} format. The detailed explanations for each record follow below.

Website

HostTypeValue
@A162.159.137.54
@A162.159.136.54
wwwCNAMEsecure.cloudways.cloud

Please make sure these are the only A and CNAME records for @ and www. Some domains also require a one-time TXT verification record, which we will send you if it applies.

Email Authentication

HostTypeValue
@TXT (SPF)v=spf1 include:_spf.elasticemail.com ~all
api._domainkeyTXT (DKIM)k=rsa;t=s;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCbmGbQMzYeMvxwtNQoXN0waGYaciuKx8mtMh5czguT4EZlJXuCt6V+l56mmt3t68FEX5JJ0q4ijG71BGoFRkl87uJi7LrQt1ZZmZCvrEII0YO4mp8sDLXC8g1aUAoi8TJgxq2MJqCaMyj5kAm3Fdy2tzftPCV/lbdiJqmBnWKjtwIDAQAB
trackingCNAMEapi.elasticemail.com
_dmarcTXT (DMARC)v=DMARC1; p=none;

If you already have an SPF or DMARC record, do not add a second one. See the Email Records section below for how to merge them.

Already manage your domain in your own Cloudflare account? There is a different, fully supported setup for that. Skip to Using Your Own Cloudflare.

Website Records

All instructions are for the base / apex domain and are in {host} -> {value} format.

We use Cloudflare Enterprise as our firewall and CDN. Setting the records below directs your site's traffic through Cloudflare, which gives you stronger security and faster load times worldwide.

A Records
@ -> 162.159.137.54
@ -> 162.159.136.54

CNAME Record
www -> secure.cloudways.cloud

Please ensure these are the only A and CNAME records for @ and www. Leftover records pointing at a previous host are the most common reason a site does not switch over cleanly.

TXT Record (only if requested)

Some domains require an additional TXT record so we can verify domain ownership. We will let you know if this applies to you, because each verification record is unique to your domain.

Email Records

All instructions are for the base / apex domain and are in {host} -> {value} format.

These records authorize the transactional email our servers send on your behalf, such as contact form notifications and account messages, so it lands in inboxes instead of spam. We use ElasticMail as our transactional email service. These records do not move your mailboxes. Your email hosting and MX records stay exactly where they are now.

SPF (TXT)

An SPF record is listed as a TXT record type in most DNS services.

If your domain already has an SPF record, add include:_spf.elasticemail.com to your existing record, making sure the line still ends with ~all. A domain should only ever have one SPF record.

If your domain does not yet have an SPF record, create a TXT record with this value: v=spf1 include:_spf.elasticemail.com ~all.

DKIM (TXT)

A DKIM record is listed as a TXT record type in most DNS services.

api._domainkey -> k=rsa;t=s;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCbmGbQMzYeMvxwtNQoXN0waGYaciuKx8mtMh5czguT4EZlJXuCt6V+l56mmt3t68FEX5JJ0q4ijG71BGoFRkl87uJi7LrQt1ZZmZCvrEII0YO4mp8sDLXC8g1aUAoi8TJgxq2MJqCaMyj5kAm3Fdy2tzftPCV/lbdiJqmBnWKjtwIDAQAB

CNAME
tracking -> api.elasticemail.com

DMARC (TXT)

Your domain may already have a DMARC record. If so, please leave it as is. Otherwise, create the following:

_dmarc -> v=DMARC1; p=none;

Using Your Own Cloudflare Account

Most clients use the standard records above, which route traffic through our Cloudflare Enterprise setup. But some teams, agencies in particular, manage their domain in their own Cloudflare account and want to keep their own proxy and traffic analytics in place. We fully support that. Here is the advanced setup.

What we will provide you

  • An origin hostname to use as your DNS target. We will send you the exact hostname for your site. It follows one of two patterns, depending on your account type:
    • Agency & white-label partners: your-site.origin.pxlhost.io
      A neutral, unbranded hostname, so the setup stays white-label when you pass these instructions along to your own client.
    • Direct FatLab clients: your-site.origin.fatlabwebsupport.com
  • A TXT verification record, only if your setup needs one. If so, we will send you the exact host and value to add.

Anywhere you see [origin-hostname] below, use the hostname we sent you.

How to set it up in Cloudflare

  1. Sign in to Cloudflare, select your domain, and open DNS → Records.
  2. Delete any existing A, AAAA, or CNAME records for the root (@) and www that point to your previous host. Leftover records are the most common cause of a switch that does not work.
  3. Add the two website records below, using the hostname we provided as the Target. Make sure both show the orange cloud (Proxied) so your proxy, firewall, and analytics stay in front of the site. Cloudflare flattens the root @ CNAME automatically, so this works at the apex.
TypeNameTargetProxy status
CNAME@[origin-hostname]Proxied (orange)
CNAMEwww[origin-hostname]Proxied (orange)
  1. Add the email authentication records from the Email Records section above. Keep the tracking CNAME and all TXT records set to DNS only (grey cloud), not proxied.
  2. Open SSL/TLS → Overview and set the encryption mode to Full (strict). This keeps the connection encrypted all the way to our origin.
  3. Let us know when you are done. We will lock our origin to Cloudflare's IP ranges, so all traffic (and all of your analytics) flows through your proxy, then confirm your site is live.

What this means for you

  • You own the firewall and WAF layer for your site. We keep server-level protections in place as a backstop.
  • Because you point at a hostname we manage rather than a fixed IP, we can move, upgrade, or relocate your server without you ever having to touch your DNS again.

Questions on any of this? Open a support ticket or reach out to your FatLab contact and we will walk through it with you.

New to DNS? Start Here

If the section above looked like a foreign language, that is completely fine. Here is what it all means in plain English.

What is DNS?

DNS is the internet's address book. When someone types your domain into a browser, DNS is what tells their computer which server to load your website from. Your domain name never changes, but DNS lets us point that name at our servers when your new site is ready.

What are these records?

  • A record connects your domain to the numeric address of the server your site lives on.
  • CNAME record is an alias that points one name (like www) at another name instead of a number.
  • TXT record is a small note attached to your domain. We use TXT records to verify ownership and to authorize the email our system sends for you.

Why does FatLab need DNS changes?

Two reasons. First, the A and CNAME records send your visitors to our servers and through our security and performance network. Second, the email records tell the world that messages sent by our system on your behalf are legitimate, so contact form notifications and other site emails do not get flagged as spam.

Where do I make these changes?

You change DNS records wherever your domain's DNS is managed. That is usually the company you bought the domain from, such as GoDaddy, Namecheap, or Network Solutions, or a DNS provider like Cloudflare if your team uses one. If you are not sure where that is, we can help you find it.

Will my website or email go down during the switch?

No. We make sure your new site is fully built and tested before any DNS change, so the switch simply redirects visitors to the finished site. And because the email records above do not touch your mailboxes, your email keeps working throughout.

How long does it take?

DNS changes usually take effect within a few minutes to a few hours as the change spreads across the internet. During a launch we keep the timing settings low so the switch happens as quickly as possible.

How We Can Help You Go Live

You do not have to do this alone. Pick whichever option is most comfortable for you.

1. We do it for you

If you can give us access to your DNS, or temporarily point your domain to us, we will make every change and confirm the site is live. This is the easiest option for most clients.

2. You make the changes

Prefer to keep control of your DNS? Use the records on this page to make the updates yourself. We are on standby to answer questions and to confirm everything looks right once you are done.

3. We walk you through it together

If you would like a hand, we can hop on a screen share and make the changes with you in real time, so nothing is left to guesswork.

Ready when you are. Open a support ticket or reach out to your FatLab contact and let us know which option you would like.

Frequently Asked Questions

Do I have to move my domain to FatLab?

No. Your domain stays registered wherever it is now. You only update a few DNS records so it points at our servers.

Will changing these records affect my email?

The records on this page do not change where your email is hosted or move your mailboxes. They only authorize the transactional email our system sends for your website. Your existing email keeps working.

What if I already have an SPF or DMARC record?

Keep the one you have. For SPF, add our include into your existing record rather than creating a second one. For DMARC, leave your current record in place. A domain should only have one of each.

Can I keep using my own Cloudflare account?

Yes. See Using Your Own Cloudflare Account above. Just reach out before go-live so we can set up your origin correctly.

I am not sure where my DNS is managed. Can you help?

Absolutely. Open a support ticket and we will help you locate your DNS and plan the switch.