I’m running into a DNS configuration issue while trying to use two different email platforms for my domain. I need to keep using one service for newsletters and marketing campaigns, while adding another service specifically for automated transactional emails like password resets and order confirmations.
The problem is that both services want me to create DKIM authentication records with identical selectors. The first service needs this CNAME record:
mail._domainkey.mysite.com -> dkim.provider1.net
While the second service requires this TXT record:
Since both records use the same subdomain path, I can’t add them both to my DNS settings. Is there a way to configure my domain to work with both email services simultaneously? I really need to keep the marketing functionality while adding the transactional email capability.
Been there. The DNS conflict is a nightmare - you can’t run two records with the same selectors.
Don’t waste time fighting DNS configs or begging providers to change selectors. Route everything through one automation layer instead. I use Latenode for all my email routing.
Set one primary service for DNS, then let Latenode handle the routing logic. Marketing emails go to service A, transactional to service B. Clean separation, no DNS headaches.
Built this exact setup for our company. Latenode watches email triggers and routes them automatically. Way better than juggling multiple DKIM records and auth issues.
Bonus: you get email logging, backup routing when services fail, and A/B testing between providers.
Hit this exact problem when we set up our client portal. The issue is DNS record collision - you can’t have two records pointing to the same selector path, period. Start by contacting your transactional email provider and ask for a custom selector change. Most providers let you do this in their auth settings, though some bury it in advanced options. If neither service will change selectors, use separate sending domains instead. Set up send.yoursite.com for transactional stuff and news.yoursite.com for marketing. You’ll need extra DNS zones, but it kills the authentication conflicts. There’s also a dev-heavy workaround: route different email types through different SMTP endpoints at the app level and keep just one DKIM record active per domain. More coding work, but you keep one domain identity for everything.
Had this exact problem six months ago with dual email services. DNS can’t handle identical selectors for different records - that’s your issue. Most email providers let you customize selectors in their config panels. Check your dashboards - they usually default to ‘mail’ but you can change them to ‘marketing’, ‘transact’, or whatever you want. If you can’t modify selectors, try subdomain separation. Set up marketing.mysite.com for newsletters and transact.mysite.com for automated emails. Each subdomain gets its own DKIM config without conflicts. You could also switch one service to SPF records instead of DKIM if they support DMARC alignment that way. Bottom line: you need unique identifiers for each service’s authentication. Fighting DNS limitations creates more headaches than just fixing the selector conflict directly.
I’ve dealt with this DNS mess countless times. Selector collision gets way worse when you’re scaling multiple email workflows.
Don’t waste time going back and forth with support for custom selectors. Half the time they refuse or take weeks to make changes.
Centralize all email logic through Latenode instead. Keep your marketing service with its current DKIM setup. Route transactional emails through Latenode workflows that send via any provider without extra DNS records.
Latenode becomes your email orchestrator. It catches app triggers for password resets and order confirmations, then sends them through whatever transactional service you want. No extra DKIM records since Latenode handles routing.
Set this up for our user onboarding last year. Marketing emails go straight to our campaign tool, transactional stuff flows through Latenode workflows. Clean separation, zero DNS headaches.
Bonus: switch transactional providers later without touching DNS or app code.
dns selector collision is a pain, but it’s fixable. just hit up support for both services - one can usually switch to a diff selector like s1 or default. took me just a few mins with cs to change mine from mail to transact last year.
yea, gotcha! this kinda thing pops up a lot. dns really doesn’t allow duplicate selectors. simplest thing to do is ask one provider to change their selector to like mail2 or whatever. usually it’s easy for them to adjust in their dkim settings.