Custom DNS on Mrfqy: MX, TXT, and advanced records for Arab merchants

Ecommerce domains rarely stop at a storefront CNAME. Arab merchants run Google Workspace on the same brand domain, verify Facebook and TikTok shops with TXT records, point a warehouse subdomain to an internal tool, and publish SPF so order emails do not land in spam. Mrfqy Custom DNS mode exposes a record manager for domains on your account — add, edit, and delete rows without logging into a third-party DNS-only product.

Enable Custom DNS assignment

Open admin → Domains → select your active domain → Assignment → Custom DNS. Save to unlock the DNS manager tab.

Switching from storefront mode stops automatic www routing — re-add a CNAME for www or shop subdomain pointing to Mrfqy if you still need the store live.

Nameservers must delegate to Mrfqy or your records must be authoritative where you edit — domains bought through Mrfqy are already on-platform.

Inactive or pending domains hide the editor — wait for ACTIVE status before adding MX for production mail.

Record types Mrfqy supports

A and AAAA map hostnames to IPv4 and IPv6 — use sparingly for storefront; prefer CNAME to Mrfqy targets unless your auditor requires static IPs.

CNAME aliases one name to another — typical pattern: www to Mrfqy edge, or shop.mybrand.com to the same target while apex keeps mail.

MX directs inbound email to Google, Zoho, or Microsoft — priority integers matter; never duplicate conflicting MX sets.

TXT holds SPF, DKIM, domain verification strings for Meta Commerce, Google Search Console, and ZATCA-related third-party tools.

Google Workspace and Zoho mail setup

Add MX records Google provides — usually five rows with ascending priorities. Delete old MX from previous host to stop split delivery.

Publish SPF TXT: v=spf1 include:_spf.google.com ~all for Google; adjust includes if you also send via Mrfqy transactional mail providers.

DKIM is a TXT record on a selector subdomain — generate keys in Google Admin, paste into Mrfqy DNS manager, wait propagation, then click verify.

DMARC optional but recommended for Saudi corporate brands — start with p=none reports before enforcing quarantine.

Shop and ads verification TXT records

Meta Commerce and TikTok Shop ask for a TXT proof on the root domain — add the exact string, avoid smart quotes from PDF instructions.

Google Search Console verification uses TXT or CNAME — TXT is faster when you already manage DNS inside Mrfqy.

Apple Pay domain verification and some BNPL providers also use hosted association files or TXT — check whether they need HTTPS on a specific path.

Remove verification TXT only after the platform shows green — re-verification is painful mid-campaign.

TTL, editing, and safe deletes

Default TTL 3600 seconds is fine for stable records — lower to 300 before cutover weekends.

Edit in place rather than delete-add when possible — some registrars treat deletes as immediate propagation events.

The manager validates host format — @ or blank often means root; follow Mrfqy field hints for Arabic RTL admin users typing Latin hosts.

Deletion requires confirmation — keep a changelog spreadsheet if multiple agencies touch the same domain.

Subdomains for ops and campaigns

blog.mybrand.com on a separate host — CNAME to your Ghost or WordPress while shop stays on Mrfqy.

wholesale.mybrand.com can point to a B2B portal later — plan hostnames before printing catalogs.

Email marketing click domains (mail.mybrand.com) need CNAME to SendGrid or Mailchimp — do not clash with storefront www.

Staging domains for agencies: test.mrfqy.store stays default; never point production MX to staging.

Switch the domain to Custom DNS, recreate MX and TXT from your mail provider, then add storefront CNAME for www. Verify mail and HTTPS in parallel before announcing the new domain publicly.