DNS Records: The MarketMYSTR Reference

DNS is the address book of the internet. When you set up MarketMYSTR — connecting a domain, configuring email, verifying text messaging — you'll touch DNS more than once. This guide explains what each record type does, which ones you actually need, and how to add them.

What is DNS?

DNS stands for Domain Name System. It's what translates yourdomain.com into the actual IP address of the server hosting your site (something like 192.0.2.45). Without DNS, the internet would require everyone to memorize IP addresses instead of domain names.

DNS records are the individual instructions that tell the internet where to route various types of traffic for your domain. Different record types handle different things — website traffic, email, verification codes, and more.

Where DNS records live. DNS records are stored at your domain registrar — the company you bought your domain from (GoDaddy, Namecheap, Cloudflare, Google Domains, Squarespace, etc.). You'll log in to that registrar's DNS control panel to add or edit records. This is different from your website host, which might be MarketMYSTR, WordPress, Wix, or something else.

Record types

There are dozens of DNS record types, but for running a business on MarketMYSTR, you only need to know five:

A record

A Address record

What it does: Points a domain or subdomain to an IP address (a numeric address like 192.0.2.45).

When you'll use it: Connecting your root domain (e.g., yourdomain.com without any prefix) to MarketMYSTR.

Example:

TypeHostValue
A@192.0.2.45

CNAME record

CNAME Canonical Name record

What it does: Points a subdomain to another domain name (rather than an IP). The target domain's DNS does the actual resolving.

When you'll use it: Connecting a subdomain (like book.yourdomain.com) to MarketMYSTR. Also used for various third-party verifications.

Important: CNAME records cannot be used on the root domain itself — only on subdomains. If you need to point the root, use an A record.

Example:

TypeHostValue
CNAMEbookconnect.marketmystr.com

TXT record

TXT Text record

What it does: Stores arbitrary text associated with your domain. Historically used for notes; today mostly used for verification codes and email authentication.

When you'll use it: Setting up email (SPF, DKIM, DMARC records), verifying domain ownership for various services, A2P registration verification in some cases.

Example:

TypeHostValue
TXT@v=spf1 include:_spf.marketmystr.com ~all

MX record

MX Mail Exchange record

What it does: Specifies where email for your domain should be delivered.

When you'll use it: Only if you're receiving email at you@yourdomain.com — and only if using a mail host like Google Workspace, Microsoft 365, or Zoho. MarketMYSTR doesn't provide inbound mailbox hosting; you'd use a separate service for that and keep those MX records pointed at it.

Warning: Don't remove your MX records when setting up MarketMYSTR. MMSTR only needs SPF/DKIM (TXT records) for sending — your MX records for receiving stay as-is.

NS record

NS Name Server record

What it does: Tells the internet which DNS servers are authoritative for your domain. Think of it as the "who's in charge of DNS for this domain" pointer.

When you'll use it: Normally you don't touch this. NS records are typically set automatically by your registrar. You'd only change them if you're moving DNS management from one provider to another (like moving DNS from GoDaddy to Cloudflare).

DNS records MarketMYSTR needs

Depending on what MarketMYSTR features you're using, you'll need different records. Here's the full map:

FeatureRecord typeWhat it's for
Subdomain connection
e.g., book.yoursite.com
CNAME Points the subdomain to MarketMYSTR's servers
Root domain connection
yoursite.com
A Points the root to MMSTR's IP address
Email sending (SPF) TXT Authorizes MMSTR to send email as your domain
Email sending (DKIM) TXT Cryptographically signs your emails (prevents spoofing)
Email sending (DMARC) TXT Tells receivers what to do with failed SPF/DKIM emails
Reply / forward domain MX (pointed at your existing inbox host) Inbound email — keep pointed at Google/Microsoft/etc.

MarketMYSTR shows you the exact values to use when you set up each feature. The values above are the types — the actual content is generated when you configure the feature.

How to add a DNS record

The UI varies by registrar, but the fields are the same everywhere:

  1. Log in to your domain registrar GoDaddy, Namecheap, Cloudflare, Google Domains, Squarespace, etc.
  2. Find the DNS settings for your domain Look for "DNS", "DNS Records", "Advanced DNS", or "Manage DNS". It's usually behind your domain's management page.
  3. Click "Add record" You'll get a form with Type, Host/Name, Value, and TTL fields.
  4. Fill in the fields
    • Type: A, CNAME, TXT, or MX — whichever MarketMYSTR told you to use.
    • Host/Name: The subdomain prefix (e.g., book) — or @ for the root.
    • Value: Copy exactly from MarketMYSTR. One typo breaks everything.
    • TTL: Leave on "Auto" or "3600" (1 hour). Don't overthink this.
  5. Save Some registrars auto-save; others require clicking Save or a green checkmark.
  6. Wait for propagation Usually 5 minutes to an hour. Can take up to 24 hours in edge cases.
  7. Verify in MarketMYSTR Return to MMSTR and click Verify. Green checkmark = done.
The #1 mistake: the Host field. For a subdomain like book.yourdomain.com, the Host field should be just book — not book.yourdomain.com. The registrar adds your domain automatically. Putting the full domain creates book.yourdomain.com.yourdomain.com, which won't resolve.

Exception: Cloudflare shows the full domain in its UI, but the field auto-extracts the prefix. Just type the full domain and Cloudflare handles it correctly.

Propagation & verification

DNS changes don't take effect instantly. They need to propagate across the internet's web of DNS servers, which can take anywhere from 5 minutes to 24 hours. Typically under an hour.

Tools to check propagation

Troubleshooting

"My record is saved but MarketMYSTR says not verified"

"I see both an A record and a CNAME for the same host — is that ok?"

No. A host can have either an A record or a CNAME, not both. DNS standards forbid it. Delete whichever one you don't need.

"My TTL is set to 86400 (24 hours). Is that bad?"

Not bad — it just means DNS caches respect that for 24 hours, so changes take longer to propagate. For initial setup it doesn't matter much. If you're planning to migrate soon, lower TTL to 300 (5 min) ~24 hours before the migration.

"Do I need to worry about record priority?"

Only for MX records (where priority matters for mail server fallback). For A, CNAME, TXT — ignore priority / preference fields, or leave them on default.

"My old website stopped loading"

You probably added a record on the same host that was already pointing somewhere else. Check for duplicates. If you removed an A record that your old site needed, put it back.