Domains and DNS
A domain has to be added to your account and verified before you can put email or a website on it. Simplewala does not sell domains — buy one from any registrar first.
Adding a domain
- Portal → Domains → Add Domain.
- Enter the bare domain:
yourbusiness.com. Nowww, nohttps://. - Add.
Verifying ownership
Adding the domain produces a verification record:
Type: TXT
Name: _simplewala-verify.yourbusiness.com
Value: simplewala-verify=abc123… Add it in your registrar's DNS settings, then click Verify Domain in the portal. The lookup runs immediately; DNS itself usually takes 5–30 minutes to make the record visible.
If your registrar asks for a “Host” or “Subdomain” rather than a full name,
enter just _simplewala-verify — the registrar appends the domain itself.
What the two states mean
| State | What you can do |
|---|---|
| Active | Create mailboxes, point apps at it, and have DNS records you add in the portal tracked. |
| Unverified | Nothing yet. The domain is on your account but ownership is not confirmed, so mailboxes are refused. |
When verification keeps failing
- The record is not there. By far the most common cause. Open the registrar's DNS page and confirm it saved.
- The name got doubled. If the record reads
_simplewala-verify.yourbusiness.com.yourbusiness.com, your registrar appends the domain for you — enter only_simplewala-verify. - The value was truncated. Copy the whole thing including the
simplewala-verify=prefix. - It is simply early. Wait 5–30 minutes and retry.
Once the domain is Active the TXT record has done its job. You can remove it, or leave it — it does no harm either way.
What each record type does
A — “this name is at this IP address”
yourbusiness.com → 185.199.10.1
www → 185.199.10.1 A website needs an A record pointing at the server's IP. This is the one people usually mean.
CNAME — “this name follows that name”
www → yourbusiness.com
shop → store.myplatform.com
For subdomains that should track another name. A CNAME cannot be used on the root domain
(@) — that is a rule of DNS, not a platform limitation.
MX — “mail for this domain goes here”
yourbusiness.com MX mail.yourbusiness.com (priority 10)
Without an MX record, mail sent to hello@yourbusiness.com has nowhere to go. See
Email hosting for the full record set.
TXT — arbitrary text, used for proofs
- Domain verification — proves you control the domain.
- SPF — names which servers may send mail as your domain.
- DKIM — a signature proving a message was not altered in transit.
- DMARC — tells receiving servers what to do when SPF or DKIM fails.
The three email ones are explained properly in SPF, DKIM and DMARC explained.
TTL — how long the rest of the internet caches the answer
| TTL | Effect |
|---|---|
| 300 (5 minutes) | Changes take effect quickly. Use while actively changing things. |
| 3600 (1 hour) | A reasonable steady state. |
| 86400 (24 hours) | Changes can take a day to be seen. |
Drop the TTL to 300 before a change, not during it — the old TTL is what governs how long the old answer sticks around. Raise it again once everything works.
Propagation
DNS servers worldwide cache records for the TTL, so a change spreads rather than switching. Typical time is 5–30 minutes. A nameserver change — moving the domain to a different DNS provider entirely — is slower, up to 24–48 hours.