Wildcard Domains & DNS Setup
EmBoux supports wildcard domains — configure DNS once for your parent domain, and every subdomain you create will work automatically without additional DNS changes.
When to Use Wildcard
Section titled “When to Use Wildcard”Use wildcard if you plan to create subdomains under a single parent domain. For example:
ganemo.com(parent, wildcard)client1.ganemo.com(subdomain — inherits DKIM from the parent)client2.ganemo.com(subdomain — inherits DKIM from the parent)
Step 1: Create a Wildcard Domain
Section titled “Step 1: Create a Wildcard Domain”When creating a domain via the API or portal, mark it as wildcard:
curl -X POST https://api.emboux.com/domains/ \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "ganemo.com"}'Then set it as wildcard (master token only):
curl -X PUT https://api.emboux.com/domains/ganemo.com/parent \ -H "Authorization: Bearer YOUR_MASTER_KEY" \ -H "Content-Type: application/json" \ -d '{"is_wildcard": true}'In the Odoo portal, simply check “I will create subdomains (wildcard)” when adding the domain.
Step 2: Configure DNS Records
Section titled “Step 2: Configure DNS Records”For wildcard domains, use * entries so all subdomains are covered:
Inbound and policy (MX + SPF + DMARC)
Section titled “Inbound and policy (MX + SPF + DMARC)”| Type | Name | Value |
|---|---|---|
| MX | *.ganemo.com | mx1.emboux.com (Priority: 10) |
| TXT | *.ganemo.com | v=spf1 include:mailgun.org ~all |
| TXT | _dmarc.ganemo.com | v=DMARC1; p=quarantine; rua=mailto:[email protected] |
The DMARC record lives at _dmarc.<parent> (here _dmarc.ganemo.com). Subdomains are covered by the parent’s policy.
Outbound (verify the parent once)
Section titled “Outbound (verify the parent once)”Verify the parent domain once with POST /domains/ganemo.com/verify. The response lists the records to publish at your DNS provider:
| Type | Name | Value |
|---|---|---|
| TXT | ganemo.com | SPF, for example v=spf1 include:mailgun.org ~all |
| TXT | <selector>._domainkey.ganemo.com | DKIM public key, exactly as returned by /verify |
| CNAME | email.ganemo.com | mailgun.org |
Use the exact values returned by /verify. Subdomains need no outbound DNS records of their own.
Step 3: Verify DNS Configuration
Section titled “Step 3: Verify DNS Configuration”Use the DNS check endpoint to verify your records are configured correctly:
curl https://api.emboux.com/domains/ganemo.com/dns-check \ -H "Authorization: Bearer YOUR_API_KEY"Response:
{ "name": "ganemo.com", "all_ok": true, "records": [ {"record_type": "MX", "name": "ganemo.com", "expected": "mx1.emboux.com", "status": "ok"}, {"record_type": "TXT", "name": "ganemo.com", "expected": "include:emboux.com", "status": "ok"}, {"record_type": "TXT", "name": "krs._domainkey.ganemo.com", "expected": "k=rsa; p=MIIBIjAN...", "status": "ok"}, {"record_type": "CNAME", "name": "email.ganemo.com", "expected": "mailgun.org", "status": "ok"} ]}Each record shows ok, missing, or incorrect.
In the portal, use the “Verify my DNS” button for a visual checklist.
Step 4: Create Subdomains
Section titled “Step 4: Create Subdomains”Once the parent is verified, create subdomains — they inherit DKIM from the parent automatically:
curl -X POST https://api.emboux.com/domains/ \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "client1.ganemo.com"}'The API auto-detects that client1.ganemo.com is a subdomain of ganemo.com and:
- Links it to the parent domain
- Inherits
outbound_tierandoutbound_enforcement - Skips separate verification (DKIM is inherited from the parent)
- No additional DNS configuration needed
Parent Domain Verification
Section titled “Parent Domain Verification”EmBoux detects the root domain and verifies it with the mail provider (Mailgun). For example, creating client1.ganemo.com verifies ganemo.com, not client1.ganemo.com.
Subdomains inherit DKIM from the parent: mail from client1.ganemo.com is signed with d=ganemo.com. You publish the verification records once for the parent, regardless of how many subdomains you create. If the parent is already verified, new subdomains are marked as verified immediately, with no extra DNS and no waiting.
Verification Status
Section titled “Verification Status”Verification is checked automatically. Once the parent is verified, outbound email is enabled for all domains under it. You can also check manually:
curl https://api.emboux.com/domains/ganemo.com/verify-status -H "Authorization: Bearer YOUR_API_KEY"Sending from a subdomain
Section titled “Sending from a subdomain”Suppose your Odoo uses a mailbox of a subdomain, such as [email protected], under a verified wildcard parent:
- Odoo sends through
mx1.emboux.com, authenticating with a mailbox of that subdomain. - The visible From address is an address of the subdomain (
[email protected]). - Reply-To can stay your own address (for example
[email protected]), so replies reach you. - Authentication comes from the parent: the message is DKIM-signed with the parent domain (
d=ganemo.com) and the parent’s DMARC applies with relaxed alignment. SPF, DKIM and DMARC pass. - You do not need to change the DNS of your own, unrelated domain, and you should not edit its SPF for this: it is not used for these emails. A strict SPF (
-all) edited by mistake can break the mail you send through other services. - The SPF of
mx1.emboux.comis irrelevant for delivery: the email goes out to the internet through the sending provider, not frommx1.
If you instead want to send as your own root domain, see Send as your own domain.
API Reference
Section titled “API Reference”| Endpoint | Method | Description | Auth |
|---|---|---|---|
/domains/{name}/parent | PUT | Set parent_domain / is_wildcard | Master |
/domains/{name}/dns-check | GET | Verify DNS records | Any |
/domains/{name}/verify | POST | Initiate domain verification | Master |
/domains/{name}/verify-status | GET | Check verification status | Any |
/domains/{name}/register-subdomain | POST | Register subdomain with provider | Master |