Set up email on a new domain with an AI agent

An AI agent can help set up email on your new domain through Banger by preparing the DNS records, guiding publishing, checking verification, and creating mailboxes. You still need authority over the domain. Publishing depends on available DNS access; the agent should present the exact records and any required human action instead of assuming access to your registrar.

The goal is a company address that can receive mail and support your product’s sending. Keep that goal concrete: one product domain, one useful mailbox, and a test you can verify before a launch audience is involved.

What the four DNS records do

MX tells other mail servers where to deliver incoming email for a domain. If you want people to reply to a company mailbox, the receiving route matters. Do not confuse mailbox MX with a sending service’s return-path MX; Banger’s setup distinguishes those records.

SPF describes which servers are authorized to send for the domain used in that authentication check. Use the value Banger prepares for your configuration. Guessing an SPF value from a tutorial for another setup can leave you with a record that does not match your sending service.

DKIM adds a cryptographic signature to outgoing mail. The matching public key is published in DNS so receiving systems can check the signature. Publish the exact selector and value from your setup, including the record type Banger specifies.

DMARC connects authentication to the visible From domain and states a policy for messages that fail the relevant checks. Banger requires a reject policy for new Banger From domains. Root-domain policy can affect other legitimate senders, so review the scope before publishing it.

Authentication is a setup requirement, not a guarantee of inbox placement. Recipients still need to expect the email, and you still need to monitor the results. The deliverability guide covers that next stage.

Steps: from domain to working mailbox

1. Connect the assistant and identify the domain

Use the MCP guide to connect Banger with scoped OAuth. Tell the assistant the exact domain, the product it belongs to, and whether it already receives or sends mail anywhere else.

Try: “Set up company email for my new product on this domain. Inspect the current setup, prepare the complete DNS bundle, and show me any conflicts before changes. I need a support mailbox and product sending.”

Calling a domain “new” should not replace inspection. You may already have verification records, another sender, or a receiving configuration from an earlier experiment. Ask the agent to preserve working services and identify conflicts explicitly.

2. Review the complete DNS bundle

Banger prepares receiving and sending records together. Ask the assistant to list each record’s host, type, value, and purpose. If the bundle is incomplete, finish preparation before asking the DNS owner to publish it.

Review existing inbox records before changing MX. Review existing SPF and DMARC configuration before introducing new policy. In particular, do not publish a second DMARC record or overwrite an existing policy without understanding the conflict.

For the root domain, identify every legitimate sender using that visible From domain. A policy change can have a wider effect than the one product message you are trying to configure. Banger’s setup calls for this review rather than treating root policy as a harmless checkbox.

3. Publish through an available path

If supported DNS automation is connected, the agent can use it to publish the records. Otherwise, use guided entry or a handoff containing the exact records for whoever controls DNS. Never paste provider secrets into the conversation to force a shortcut.

Check how your DNS provider expects hostnames to be entered. Compare the saved record with Banger’s required hostname and value after publishing. Confirm that the published DNS matches the requested configuration.

Existing-service replacements require the appropriate human migration approval. Even for a small launch, moving receiving email is a different decision from adding authentication for a new sender. Keep those changes visible and deliberate.

4. Verify and distinguish pending states

Ask the agent to run verification after the approved records are saved. If records remain pending, inspect the returned details. A recently saved record may still be propagating, but an incorrect hostname or value needs a correction.

When all records are verified but readiness is still pending, inspect provider activation status. Do not repeatedly rewrite correct DNS records because another activation step has not finished. Ask the assistant to report the actual state and its last check.

This distinction keeps setup from becoming a loop of unnecessary edits. “DNS missing,” “DNS verified,” and “sending ready” describe different points in the process.

5. Create mailboxes and prove the result

Create the company mailbox you need and test receiving as well as sending. Banger’s setup includes a real round-trip activation check. Follow the returned workflow and inspect the evidence rather than declaring success because the DNS screen looks complete.

Use a recipient you control for your own first message. Check the visible sender, reply destination, links, and delivery status. Then connect application-driven email using the API reference or prepare a welcome Journey through your agent.

Keep the first launch within its limits

Inboxes are free and unlimited on every plan. Free includes 3,000 monthly sends with a 100-email daily cap; sends beyond that daily cap go out the next day. Paid plans refuse sending past their monthly allowance until renewal or upgrade, without overage or usage fees.

Check pricing before scheduling the launch. Separate mailbox names can help people recognize support and product messages, but they do not multiply the workspace’s allowance or remove suppressions.

FAQ

Does my agent automatically control my DNS provider?

No. Publishing depends on supported, authorized access. Otherwise Banger provides guidance or a handoff for the DNS owner.

Is MX enough to send authenticated email?

No. Receiving routes and sending authentication serve different purposes. Publish and verify the complete setup Banger prepares.

Should I keep editing records while activation is pending?

Only correct records that the returned checks show are wrong. If DNS is verified, inspect activation status instead of repeatedly changing working records.

Does verified DNS guarantee delivery to the inbox?

No. It establishes the relevant configuration. Consent, message purpose, recipient response, and sending behavior still matter after setup.