Online OrderingSetup GuideIntermediate

Run your ordering website on your own domain

Last verified: 2026-09-07

Run your ordering website on your own domain

Every MyFoodFast account comes with a ready-to-use ordering website at yourname.myfoodfast.co.uk. It works from day one and needs no setup from you.

When you're ready, you can move your ordering site onto your own web address instead. You have two choices, and both are fully supported.

Choose your address

OptionExampleBest when
A subdomain of your domainorder.yourbusiness.co.ukYou already have a website on yourbusiness.co.uk that you want to keep
Your full (root) domainyourbusiness.co.ukYour MyFoodFast site is your website — customers type your domain and land straight on your menu

Tip: If you don't have a separate website — or you have an old brochure site you're happy to retire — use your full domain. It's the shortest address to say on the phone, print on a menu, or put on a shopfront.

Choosing your full domain does not affect your email. Your email keeps working as long as you leave your existing MX and TXT records alone.

Step 1: Tell us the address you want

Email help@myfoodfast.com with the exact address you'd like to use, for example:

"I'd like my ordering website on yourbusiness.co.uk"

or

"I'd like my ordering website on order.yourbusiness.co.uk"

We'll add it to your account and reply with the exact DNS record to create. Wait for that reply before you change anything — the record values are specific to your account, and the certificate can't be issued until the address is on your account.

Note: Just want a different myfoodfast.co.uk subdomain (for example pizzatime.myfoodfast.co.uk)? Email us the name you want. There are no DNS changes for you to make — we handle it entirely.

Step 2: Add your DNS record

Log in to your domain registrar or DNS provider (GoDaddy, Namecheap, Cloudflare, 123 Reg, IONOS, or whoever manages your domain) and add the record we sent you in Step 1.

Important: Use the values from our reply, not values you found elsewhere. The target address and IP differ between accounts, and the certificate check looks for the exact record your account expects — a record copied from another guide will fail verification even though it looks correct.

The sections below explain what you'll be adding, so you know what you're looking at.

If you chose a subdomain

One CNAME record:

SettingValue
TypeCNAME
Name / Hostorder (or your chosen subdomain — orders, food, menu)
Target / Points toThe address in our reply — it looks like 46fa3ba6f4278da2.vercel-dns-017.com
TTLAuto (or 300)

Important: If an A or AAAA record already exists for that same name, delete it first. A CNAME can't coexist with an A or AAAA record on the same name.

If you chose your full (root) domain

A root domain — also called the apex, the naked domain, or @ — can't normally use a CNAME. How you point it depends on your DNS provider.

Option A — your provider supports ALIAS, ANAME, or CNAME flattening (recommended). Cloudflare, DNSimple and Route 53 all do; Cloudflare applies it automatically when you enter a CNAME at the root. Point it at the same target we sent you for a subdomain:

SettingValue
TypeALIAS / ANAME / CNAME (whichever your provider offers at the root)
Name / Host@ (or blank, or your domain name — providers label this differently)
Target / Points toThe address in our reply
TTLAuto (or 300)

Option B — your provider only supports A records at the root. Use the IP address from our reply:

SettingValue
TypeA
Name / Host@
Value / Points toThe IP in our reply — a four-part number such as 76.76.21.21
TTLAuto (or 300)

Then add www as well. Whichever option you used, add a second record so www.yourbusiness.co.uk works too:

SettingValue
TypeCNAME
Name / Hostwww
Target / Points toThe same target address from our reply
TTLAuto (or 300)

We'll set www to redirect to your root domain, so customers land in the same place either way.

Warning: Pointing your root domain at MyFoodFast replaces whatever yourbusiness.co.uk currently shows. If you have an existing website there, it will stop being reachable at that address once DNS updates. Make sure that's what you want before you change the record — and if you'd rather keep both, use a subdomain instead.

Note: Leave your MX records and any email-related TXT records (SPF, DKIM, DMARC) exactly as they are. Only change the A / ALIAS / CNAME records described above.

Step 3: Cloudflare users — one extra setting

If Cloudflare manages your DNS, you must change one setting or your site will show a "redirected you too many times" error.

  1. Log in to Cloudflare and select your domain.
  2. Go to SSL/TLS > Overview.
  3. Set the encryption mode to Full (strict).

Why this matters

With Cloudflare's default "Flexible" mode:

  1. A customer visits https://yourbusiness.co.uk
  2. Cloudflare connects to our servers over HTTP
  3. Our servers redirect to HTTPS
  4. Cloudflare sees the redirect and connects over HTTP again
  5. The loop repeats and the customer sees an error

Full (strict) fixes it immediately.

Proxy setting (orange cloud vs grey cloud)

SettingNotes
DNS only (grey cloud)Recommended. Traffic goes directly to our servers.
Proxied (orange cloud)Works, but only with SSL/TLS set to Full (strict).

Step 4: Wait and check

  • DNS changes usually take 5–30 minutes to take effect (occasionally up to 24 hours).
  • Your SSL certificate is issued automatically once DNS is live — nothing for you to do.
  • Check your record has propagated at dnschecker.org.
  • Visit your new address in a browser and confirm the padlock shows.

Reply to Support once it loads and we'll verify everything end to end.

Warning: Once your own domain is live, your old yourname.myfoodfast.co.uk address stops working completely — anyone using an old link gets a connection error rather than being forwarded. Before you switch, ask us to put a redirect in place from the old address, and update your printed menus, leaflets, Google Business Profile and social media links.

Provider guides

Troubleshooting

"This page isn't working" / ERR_TOO_MANY_REDIRECTS

Almost always a Cloudflare SSL setting.

  • Cloudflare users: set SSL/TLS to Full (strict) — see Step 3.
  • Other providers: check your provider isn't forcing its own HTTP to HTTPS redirect on top of ours.
  • Clear your browser cookies or open an Incognito / Private window.

Site not loading / "Server not found"

  • Check the record matches our reply character for character — no trailing dot, no typos, and no value copied from another guide.
  • Make sure no conflicting A or AAAA record exists for the same name.
  • On a root domain, check your provider hasn't kept a default "parking" or "under construction" A record.
  • Allow up to 24 hours for full propagation, though it's usually 5–30 minutes.

www works but the root domain doesn't (or the other way round)

You've only created one of the two records. Go back to Step 2 and add the missing one.

SSL certificate error / "Not Secure"

  • Certificates are issued automatically after DNS is correct — allow up to 30 minutes.
  • If it's been over an hour, email us and we'll check.

Still seeing your old website

  • Chrome: open chrome://net-internals/#dns and click Clear host cache, then chrome://net-internals/#sockets and Flush socket pools.
  • Reload with Ctrl+F5, or try an Incognito window.

Migrating from another provider

  • Lower your TTL to 300 seconds the day before you switch.
  • Make the change during off-peak hours.
  • Keep your old site online for around 24 hours as a safety net.

Common questions

Can I keep my existing website and still use my own domain? Yes — use a subdomain like order.yourbusiness.co.uk. Your main site at yourbusiness.co.uk is untouched.

Will moving my domain break my email? No, as long as you leave your MX and email TXT records alone. Only change the records listed in Step 2.

Can I use more than one domain? Yes. Let Support know and we can point several addresses at your ordering site, with one set as the main address.

What happens to customers who have my old myfoodfast.co.uk link saved? The old address stops resolving once your own domain takes over, so they'd hit a connection error. Ask us to set up a redirect from it when we make the switch — we can forward the old address to your new one.

How long does the whole thing take? Usually under an hour: a few minutes for us to add the domain, 5–30 minutes for DNS, and the certificate issues automatically.

Was this helpful?