DNS setup for Bento

Authenticate your domain so Bento can send on your behalf, keep Gmail/Yahoo compliant, and stop spoofing before it starts.

Proper DNS records are no longer optional. Gmail and Yahoo require authentication for anyone sending more than 5,000 messages per day—and honestly, you should set them up regardless of volume. Once live, Bento automatically signs email with these records and routes tracking links through your domain.

Why DNS configuration matters

  • Improves deliverability—authenticated senders gain inbox trust.
  • Prevents spoofing—receivers can prove the message genuinely came from you.
  • Builds long-term reputation—consistent DNS means fewer spam-folder surprises.
  • Avoids new Gmail/Yahoo enforcement penalties.

DNS provider guides

Follow the step-by-step instructions for your host. Each guide shows screenshots, record examples, and provider-specific gotchas.

Cloudflare

Proxy-aware setup with grey-cloud CNAMEs.

Open guide →

GoDaddy

Classic registrar UI with Host / Points-to fields.

Open guide →

Hover

Simple interface for creators and small teams.

Open guide →

Namecheap

Save each record with the green checkmark.

Open guide →

AWS Route 53

Infrastructure-as-code friendly hosted zones.

Open guide →

Required DNS records

CNAME records (4 required)

  • Handle domain verification and link tracking.
  • Each subdomain points to a Bento-managed hostname.
  • TTL 3600 seconds keeps propagation reasonable without being noisy.

TXT records (2 required)

  • SPF & DKIM prove Bento can send on your behalf.
  • TXT strings are long—copy/paste directly from the dashboard to avoid typos.

General setup instructions

  1. Add your sending domain inside Settings → DNS to generate the record set.
  2. Open your provider's DNS management console for that domain.
  3. Create the four CNAME records exactly as Bento lists them (host + target).
  4. Add the DKIM + DMARC TXT records, keeping the values intact (quotes included if your provider requires them).
  5. Wait for propagation—many providers finish within minutes, but allow up to 48 hours.
  6. Return to Bento and click “Verify” next to each record until all turn green.

Troubleshooting common issues

Records not found
  • Give propagation more time—some networks cache for hours.
  • Double-check hostnames; providers often add the root domain automatically.
  • Keep TTL at or below 3600 so you can retry quickly.
  • Confirm you're editing the correct DNS zone (especially if you manage subdomains).
Partial verification
  • Validate each record individually with a lookup tool before retrying Bento's checker.
  • TXT formats vary—some panels require wrapping values in quotes.
  • CNAME entries should not include trailing periods unless your provider explicitly wants them.
  • If you still cannot locate the record, contact your DNS host to confirm formatting requirements.
Propagation delays
  • Lower TTL before creating records if your provider allows changes.
  • Flush your local DNS cache or test from another network.
  • Use tools like DNSChecker or WhatsMyDNS to compare regions.
Provider-specific quirks
  • Cloudflare: disable the orange cloud proxy (set records to DNS-only).
  • GoDaddy: use @ for the root domain in CNAME entries and save after each change.
  • Namecheap: click the green checkmark to persist the record—navigating away discards it.
  • Route 53: ensure your IAM role can edit the hosted zone; otherwise updates silently fail.

Testing your DNS records

Use online tools for a quick gut-check, then verify from your terminal for source-of-truth results.

  • DNSChecker — Global view for CNAME/TXT propagation.
  • WhatsMyDNS — Quick propagation spot-check. 
# Check CNAME records
dig CNAME example.yourdomain.com

# Check TXT records
dig TXT yourdomain.com

# Query a specific resolver
dig @8.8.8.8 TXT yourdomain.com

DNS propagation timeline

0–15 minutes

Records start resolving within your primary region—great time to smoke-test.

15–60 minutes

Most global resolvers catch up; verification often passes here.

1–4 hours

Stubborn ISP caches clear. Keep monitoring if you changed TTL after the fact.

4–48 hours

Outliers (corporate networks, legacy ISPs). Open a ticket only after this window.

Next steps

  1. Send a test email once all checks turn green.
  2. Monitor deliverability in Bento's dashboard for the first few sends.
  3. Leave the records alone—consistency is the heart of reputation.
  4. Scale confidently knowing your domain is authenticated.

Need help?

Run into something odd? Open the provider guide above, hop into the Bento Discord, or contact support inside the app. Share screenshots of your DNS panel and we will walk through verification together.