Connect your own domain
Show your store at a domain you own, like www.yourbusiness.com or yourbusiness.com.
Storefront Domain is on the Business page, near the end. Its buttons act straight away; the page's Save doesn't include it.
- Go to Business → Storefront Domain and select Connect Domain.
- Enter your domain in Your Domain: www.yourbusiness.com, another subdomain such as shop.yourbusiness.com, or the bare domain yourbusiness.com. Select Save.
- At your domain provider (GoDaddy, Namecheap, Cloudflare and so on), add the records shown, using the exact Host / Name and Points to / Value. Records are grouped by address: your main address first, then the address that forwards to it. A subdomain needs one CNAME record. Its Host / Name is everything before your bare domain: www for www.yourbusiness.com, and order.shop for order.shop.yourbusiness.com. When Bakebug recognizes your DNS provider (GoDaddy, Namecheap, Squarespace, Wix, IONOS, Cloudflare or Porkbun), a short tip for that provider shows under the record.
- Bakebug checks automatically. You can also select Check DNS: one check covers both addresses (www and the bare domain) and your domain's email (MX) records. Each record then shows Found with a tick, or Not Right Yet with a cross and what is there instead (for example "Bakebug can't see it yet", "points to … instead. Edit that record" or "GoDaddy forwarding is on for www. Turn it off, then add this CNAME"). When the value at your provider is almost Bakebug's (one or two characters different, or your domain added to the end of it), the record shows Almost instead, says what differs (for example "one character is different … it's missing an "x" after …"), and shows Yours and Bakebug's one above the other with the difference marked. Select Copy Bakebug's Value and paste it over the old value at your provider rather than typing it. A value that is another CloudFront address is named as "a different CloudFront address, not Bakebug's". If your domain's DNS doesn't answer within a few seconds, the check says the address "could not be checked. Try again in a few minutes." and nothing is started.
- The status moves from Needs DNS Records to Securing Your Domain to Live. Bakebug usually sees a saved record within a few minutes, and the page updates by itself, so you can leave it: it looks every 10 seconds (up to once a minute while your DNS is slow to answer), pauses while the tab is in the background and looks again when you come back to it. Securing Your Domain usually takes 5 to 30 minutes and needs nothing from you: Bakebug gets your domain its own HTTPS certificate and puts it in place. The status says Live only once that certificate is in place, so visitors never see a security warning. While the domain shows Needs DNS Records, Bakebug looks for your records every few minutes in its first week, then once a day until day 30, then once a week. If it still says Needs DNS Records after a day, contact support@bakebug.com. If the HTTPS certificate can't be issued after 3 tries (usually because something else answers for the domain, such as a registrar redirect), the card says so: check the records on the card, then remove the domain and add it again.
Once your domain is Live, your bakebug.com store link forwards visitors to it, and links in your texts and emails use it. The Shop QR Code in the account menu uses it from then on too. The card then shows one sentence, such as "yourbusiness.com is live; www.yourbusiness.com forwards to it.", and folds the records away under Show DNS Records (open it to see the records or select Check DNS again).
Bare domains (yourbusiness.com)
A bare domain can't have a CNAME record, so it works only when your DNS provider offers an ALIAS, ANAME or flattened CNAME record at the bare domain. Cloudflare is the provider we have tested end to end. Amazon Route 53, DNSimple, DNS Made Easy, Netlify, Porkbun, Namecheap, Gandi, Name.com, ClouDNS, easyDNS, Hurricane Electric and Vercel offer these records too and are supported. GoDaddy, Squarespace, Wix, IONOS, Bluehost, HostGator, Hover, WordPress.com and DigitalOcean don't; if your DNS is at one of those, Bakebug says so when you select Save, and you connect www instead (below).
- Connect the bare domain: enter yourbusiness.com. The page names your DNS provider and shows two records: the bare-domain record (Host @, type ALIAS, ANAME, CNAME on Cloudflare, or an A record with Alias on Route 53) and a TXT record named _cf-challenge, both with the value shown. Both are required. On Cloudflare, set Proxy status to DNS only (grey cloud). Remove any other A or AAAA records for the bare domain, and turn off forwarding or parking for it.
- www comes along: Bakebug also connects www.yourbusiness.com and forwards it to yourbusiness.com. Add the CNAME record shown under "www.yourbusiness.com (forwards to yourbusiness.com)". It has its own status. Remove on the www.yourbusiness.com row (confirm with Remove) stops the forwarding without touching your store's domain.
- Already on www? Open "Want yourbusiness.com (no "www") to work too?" and select Connect Bare Domain under "Connect yourbusiness.com here", then add the two records shown. The bare domain forwards to your www address. Your www domain keeps working throughout.
- Once both records are in place, the bare domain usually reaches Live within about 10 minutes.
- Moving your DNS to a new provider (for example Cloudflare)? Keep your old provider's forwarding switched on for 24 hours after you change nameservers: some internet providers keep using the old nameservers for up to a day. Also check that your email records came across, including any record your MX points to (for example emailfwd). Check DNS warns "No email (MX) records found" when your domain has none: email to your @yourbusiness.com addresses may stop arriving until you add your email provider's MX records at the new provider. Your storefront isn't affected. If your Email Sending Domain is the same domain, the warning says so, since replies to your sending address need these records too.
Choose your main address
Once both addresses are Live, the card offers to make yourbusiness.com (or the www address, whichever forwards now) your main address: select Make Main Address and confirm in the dialog. Your store moves to that address and the other one forwards to it. Both keep working throughout, with no downtime, and links you already sent keep working. New links in texts and emails use the new main address, so a bare domain makes each text link 4 characters shorter. You can switch back after a few minutes.
If your provider can't do it, forward the bare domain to your www address instead. Open "Want yourbusiness.com (no "www") to work too?" on the page (it shows your own domain):
- Option 1: Your Domain Provider's Forwarding. Forward only the bare domain (yourbusiness.com) to https://www.yourbusiness.com, as a permanent (301) forward with masking off. Never add forwarding for www: forwarding on www stops it from reaching Bakebug, and two forwardings that point at each other make a redirect loop. Some providers forward only plain HTTP, so a visitor who types https://yourbusiness.com may see a warning. On GoDaddy the card lists the steps: open your domain's DNS page, select the Forwarding tab, delete any forwarding for www, then add forwarding for the domain to https://www.yourbusiness.com with Permanent (301) and Forward only.
- Option 2: A Free Redirect With Cloudflare (works with HTTPS). Most people only need Option 1. Create a free Cloudflare account, add your domain and change its nameservers to Cloudflare's at your registrar (Cloudflare copies your records). Add a proxied (orange cloud) A record for the bare domain pointing to 192.0.2.1. Then under Rules → Redirect Rules, create a rule for requests to yourbusiness.com that redirects to https://www.yourbusiness.com with status 301 and the path and query kept. Your www CNAME stays DNS only. Once your DNS is on Cloudflare you can also connect the bare domain here directly instead.
One domain at a time. To use a different domain, select Remove Domain and confirm with Remove: your store goes back to its bakebug.com link and the domain, with its www or bare-domain forwarding, stops working. If you sent marketing texts in the last 61 days, those texts link to this domain (or to the other address, if you switched your main address). You'll be asked to choose Keep Forwarding (until the date the dialog shows; recommended) or Release Now. Keeping it moves your store back to bakebug.com, and the domain forwards visitors there until that date. Keep the domain registered and pointed at Bakebug until then. You can connect a different domain once it is released, or sooner with Release Now. Removing only the forwarding address asks the same question when recent texts link to it.
Texts and emails. Links in your texts and emails use your main address; the Texts and Emails note on the card says how many characters it adds to each text link compared with bakebug.com. A domain that mobile carriers may block makes texts use bakebug.com instead; the page tells you if that applies. The address your emails come from is set separately, under Email Sending Domain.
Emails about your domain. Bakebug emails your login address once when your domain goes Live ("yourbusiness.com is live"). If it still shows Needs DNS Records about 24 hours after you added it, you get one email saying what its DNS is still missing, with the records to add. After your domain is Live, Bakebug keeps checking its DNS about every 6 hours. If its records stop pointing to Bakebug (for example a new website builder or an expired domain replaced them) and stay that way for 6 hours, you get one email ("yourbusiness.com no longer points to Bakebug") saying what is there instead, with the records it needs; your bakebug.com link keeps working meanwhile. Put the records back and nothing else is needed; if it breaks again later, you get another email. Bakebug also checks a Live domain's HTTPS certificate about once a day and fixes it by itself if it's missing; if a new certificate is needed, the status shows Securing Your Domain again until it's in place (no email). These are account emails, so the Account → Notification Preferences switches don't turn them off.
Troubleshooting. While an address shows Needs DNS Records, the page says what its DNS is still missing, read straight from your DNS provider's own servers, so a record you just saved counts right away. For example: no record yet; the domain "still points to" an address that isn't Bakebug's (an old A record, forwarding or parking, with the address named); Cloudflare's proxy is still on; the _cf-challenge TXT record isn't visible yet or has a different value; or a subdomain's CNAME points somewhere else. Fix that record, then select Check DNS again. When the page recognizes what is there, it names it:
- Forwarding is on for www (GoDaddy). The record says "GoDaddy forwarding is on for www", with GoDaddy's forwarding addresses (15.197.225.128 and 3.33.251.168). Nothing is wrong with your computer: www is still forwarding somewhere else. While that forwarding exists, GoDaddy locks its A records ("You can't modify records that have been applied by a product or service") and rejects the CNAME as "Invalid data". In GoDaddy, open your domain's DNS page. On the Forwarding tab, delete the forwarding for www. Then on the DNS Records tab, add the CNAME record from the card; GoDaddy removes the forwarding's A records by itself within a few minutes. If you also want the bare domain to work, forward only the bare domain to https://www.yourbusiness.com (Option 1 above).
- An old website (Squarespace or Wix). The record says www "still points to a Squarespace website" (or Wix). Delete those A records for www at your DNS provider, then add the CNAME. If www has a CNAME to your old site (for example ext-cust.squarespace.com), edit that record instead.
- A default or parking record. GoDaddy adds a www CNAME that points to your bare domain (its value shows as @); Namecheap and Porkbun add parking records. Edit that existing www record and change its value; don't add a second one. If Porkbun's parking uses A records instead, the record says www "still points to Porkbun's parking page": delete those A records for www, then add the CNAME.
- Something else (addresses the page doesn't know): usually domain forwarding or an old website. Turn off any forwarding for that address at your provider and delete its A records, then add the CNAME.
- Records right, but the status says DNS Provider Issue. Bakebug's own check finds your records, but our certificate provider's check refuses the answer your DNS provider gives for them (seen with WordPress.com's nameservers, which add extra records of their own). For the first hour after your records appear, the card says "Your records for this domain are in place, but our certificate provider doesn't see them yet": new records can take up to an hour to reach it, and there's nothing to do. If it still refuses after an hour, the status changes to DNS Provider Issue and the card names your provider and what to do: ask its support to stop adding records for that address, or move your domain's DNS to another provider (your registrar's own DNS, or Cloudflare's free plan), add the records shown there and select Check DNS. Bakebug keeps trying by itself every few minutes, and our team is alerted if it lasts a day.
- "This store is temporarily unavailable" on a connected domain means Bakebug couldn't look the domain up for a moment (nothing is wrong with your records). The page works again on its own within a minute; your bakebug.com link keeps working too.
If securing your domain can't finish (for example, your record pointed somewhere else while it was being set up), Bakebug starts it again automatically: the status goes back to Needs DNS Records and moves on once your record is right. You don't need to remove the domain. If a connection attempt doesn't finish, the card says why in plain words and Bakebug tries again by itself; if a message stays for a day, contact support@bakebug.com. Setting up a storefront domain is separate from your Email Sending Domain; they use different DNS records.
DNS words, in short. A CNAME record points a name such as www at another name (Bakebug's address). An A record points a name at a numbered internet address; forwarding and website builders add these. An ALIAS or ANAME record is a CNAME that some providers allow on the bare domain. A TXT record holds text; Bakebug's _cf-challenge TXT record proves the bare domain is yours. In the Host / Name field, @ (or a blank host at some providers) means the bare domain itself.
Still need help?
Email support@bakebug.com with your store name and order number (if it's about an order), or ask other bakers in the Bakebug Community.