export const dnsSection = '/docs/images/dns/route53/rt-dns-section.webp'
export const cnameSection = '/docs/images/dns/route53/rt-add-cname.webp'
export const textSection = '/docs/images/dns/route53/rt-add-text.webp'
export const recordList = '/docs/images/dns/cloudflare/cf-record-list.webp'


# Setup AWS Route 53 DNS for Bento

This guide will walk you through configuring the required DNS records in AWS Route 53 to authenticate your domain for Bento email sending. By adding these records, you'll ensure optimal email deliverability and prevent your emails from being marked as spam. 


> ⚠️ **Warning**
> Adding DNS records is required for any customer sending over 5,000 emails on any given day. This is a new requirement from Gmail and Yahoo introduced in February 2024.


## Prerequisites

Before starting, ensure you have:
- Access to your AWS account with Route 53 permissions
- Your domain configured as a hosted zone in Route 53
- IAM permissions to create and modify DNS records

## Required DNS Records

You'll need to add 6 DNS records to your domain to begin sending emails with Bento:


  ```
  example              CNAME  example.test.sendgrid.net
  bbb._domainkey       CNAME  bbb.domainkey.example.test.sendgrid.net
  bbb2._domainkey      CNAME  bbb2.domainkey.example.test.sendgrid.net
  bento                CNAME  ga.bentoemail.com
  bento3180._domainkey TXT    k=rsa; p=example...
  _dmarc               TXT    v=DMARC1; p=quarantine; adkim=s
  ```


You can find your specific DNS records in Bento under `System > DNS`. The values above are examples - use the actual values provided in your Bento account.


  
**1. Access Route 53 Hosted Zones**

  
    
      
        <ol className="space-y-2">
          <li>Log into your AWS Management Console</li>
          <li>Navigate to <strong>Route 53</strong> service (search for "Route 53" in the services menu)</li>
          <li>Click on <strong>Hosted zones</strong> in the left sidebar</li>
          <li>Find and click on your domain name from the list</li>
          <li>You'll see the DNS records management interface for your hosted zone</li>
        </ol>
        
        
> If you don't see your domain listed, you'll need to create a hosted zone for your domain first. This typically costs $0.50/month per hosted zone.

      
      
        <div className="bg-zinc-800 border border-zinc-700 rounded-lg px-2 pb-1 text-center">
          
        </div>
      
    
  

  
**2. Create CNAME Record Sets**

  
    
      
        You'll need to add 4 CNAME records. Let's start with the first one:
        
        <ol className="space-y-2">
          <li>Click the <strong>Create record</strong> button</li>
          <li>In the <strong>Record name</strong> field, enter: <code>example</code></li>
          <li>Select <strong>CNAME</strong> from the Record type dropdown</li>
          <li>In the <strong>Value</strong> field, enter: <code>example.test.sendgrid.net</code></li>
          <li>Set <strong>TTL</strong> to <strong>300</strong> seconds (5 minutes)</li>
          <li>Click <strong>Create records</strong></li>
        </ol>

        
> Route 53 uses "Record name" for the subdomain and "Value" for the target. The system automatically appends your domain to the record name.


        Repeat this process for the remaining CNAME records for example:
        - `bbb._domainkey` → `bbb.domainkey.example.test.sendgrid.net`
        - `bbb2._domainkey` → `bbb2.domainkey.example.test.sendgrid.net`
        - `bento` → `ga.bentoemail.com`

        
> 🚨 **Important**
> The example domain is for demonstration purposes only. Please use your own domain records from Bento <code>SYSTEM -> DNS</code> in the menu.

      
      
        <div className="bg-zinc-800 border border-zinc-700 rounded-lg px-2 pb-1 text-center">
          
        </div>
      
    
  

  
**3. Create TXT Record Sets**

  
    
      
        Now you'll add 2 TXT records. Let's start with the DKIM record:
        
        <ol className="space-y-2">
          <li>Click the <strong>Create record</strong> button</li>
          <li>In the <strong>Record name</strong> field, enter: <code>bentoEXAMPLE._domainkey</code></li>
          <li>Select <strong>TXT</strong> from the Record type dropdown</li>
          <li>In the <strong>Value</strong> field, enter the full DKIM key (starts with k=rsa; p=...)</li>
          <li>Set <strong>TTL</strong> to <strong>300</strong> seconds</li>
          <li>Click <strong>Create records</strong></li>
        </ol>

        Then add the DMARC record:
        <ol className="space-y-2">
          <li>Click <strong>Create record</strong> again</li>
          <li>In the <strong>Record name</strong> field, enter: <code>_dmarc</code></li>
          <li>Select <strong>TXT</strong> from the Record type dropdown</li>
          <li>In the <strong>Value</strong> field, enter: <code>v=DMARC1; p=quarantine; adkim=s</code></li>
          <li>Set <strong>TTL</strong> to <strong>300</strong> seconds</li>
          <li>Click <strong>Create records</strong></li>
        </ol>

        
> ⚠️ **Warning**
> For TXT records with long values (like DKIM keys), ensure the entire value is enclosed in quotes. Route 53 will automatically handle this, but verify the value is complete.

        
> Pro-tip: You can copy the exact DNS record values from your Bento account by clicking on each record. This helps avoid typos that could prevent verification.

      
      
        <div className="bg-zinc-800 border border-zinc-700 rounded-lg px-2 pb-1 text-center">
          
        </div>
      
    
  

  
**4. Verify Your DNS Records**

  
    
      
        After adding all 6 DNS records, you need to verify them in Bento:
        
        <ol className="space-y-2">
          <li>Return to Bento and navigate to <strong>`SYSTEM ->DNS`</strong></li>
          <li>Wait 5-10 minutes for DNS propagation (Route 53 is typically fast)</li>
          <li>Click the <strong>Check</strong> button next to each DNS record</li>
          <li>Properly configured records will show a green checkmark and blue text</li>
          <li>If any records fail verification, double-check the values and TTL settings</li>
        </ol>

        
> Route 53 DNS changes typically propagate within 60 seconds globally, but it can take up to 48 hours in some cases. If records don't verify immediately, wait a bit longer and try again.


        
> 🚨 **Important**
> DO NOT EDIT EXISTING RECORDS FOR YOUR DOMAIN. You should only be ADDING new records, never editing existing ones.

      
      
        <div className="bg-zinc-800 border border-zinc-700 rounded-lg px-2 pb-1 text-center">
           DNS'} imgWidth={'1200'} />
        </div>
      
    
  

  
**5. Final Record Overview**

  
    Once complete, your Route 53 hosted zone DNS records should be as follows:

    All 6 records should be visible in your hosted zone with:
    - 4 CNAME record sets with proper Record name and Value fields
    - 2 TXT record sets with proper Record name and Value content
    - All records showing TTL of 300 seconds
    - Status showing as "INSYNC" (successfully created)
  


## Route 53 Notes

- **Record Sets**: Route 53 uses "record sets" terminology instead of just "records"
- **Hosted Zones**: Your domain must be configured as a hosted zone in Route 53
- **Propagation**: Route 53 typically propagates changes within 60 seconds globally
- **IAM Permissions**: Ensure your AWS user has Route53:ChangeResourceRecordSets permission

## Troubleshooting

If you encounter issues:

- **Records not verifying**: Double-check that all values match exactly what is shown in your Bento account
- **Hosted zone missing**: Create a hosted zone for your domain in Route 53 first
- **Permission errors**: Verify your AWS user has the necessary Route 53 IAM permissions
- **DNS propagation**: Route 53 is fast, but wait up to 48 hours for global propagation
- **TTL settings**: Use 300 seconds (5 minutes) for faster propagation during setup

## Next Steps

Once all DNS records are verified in Bento:
1. Your domain is now authenticated for email sending
2. You can start sending emails with improved deliverability
3. Monitor your email performance in the Bento dashboard

If you have any questions, feel free to ask in the Bento [Discord](https://discord.gg/ssXXFRmt5F)!