To send your messages from edrone with good deliverability, you need to add your sending domain in the system and authenticate it by creating the right DNS records with your provider.
This applies when your domain's DNS is hosted on Azure DNS. Prerequisite: you need a DNS Zone on Azure for the domain, already delegated to Azure (see the delegation section below).
📌 Tip: your sending domain is not your store's URL. It doesn't include "https://" or "www" and can differ from your store domain — but it must be the domain you use to send your messages. Example: yourstore.com
Step 1 – Configure DNS records automatically in edrone
Go to Settings › Sending domain in your edrone Control Panel. If your domain isn't added yet, click Add domain and enter the domain you use for your messages. Click Configure DNS records and then Go to DNS setup. Keep this window open.
📌 Tip: Azure DNS accepts NS records per subdomain — unlike Registro.br. So edrone's recommended setup (NS per subdomain) works on Azure: create a record set with Type = NS, Name = the subdomain edrone gave you (e.g. mailing) and Value = the NS values edrone provided. If you prefer, use the CNAME/TXT alternative instead.
Step 2 – Adding the records in Azure DNS
Path: portal.azure.com › DNS zones › [zone] › + Record set › + Add
Log in to the Azure portal (portal.azure.com).
In the top search bar, type DNS zones and select the result.
Select the domain's zone (e.g. yourstore.com).
On the Overview page, click + Record set.
Click + Add and fill in the Add record set page as edrone shows you: Name (the host edrone gave you, e.g. mailing, edr._domainkey — use @ for the root domain), Type (NS, CNAME or TXT), TTL (3600 seconds / 1 hour), and Alias (CNAME), Value (TXT) or Name servers (NS) — paste the exact value from edrone, without extra spaces.
Click Add. Repeat for each record edrone provided.
Go back to edrone and click Verify records.
Delegation — pointing the domain to Azure DNS
For Azure to answer for your domain, its NS needs to point to Azure's servers. This is done once, at the registrar.
In the Azure portal, open the DNS Zone and, on Overview, copy the 4 name servers (ending in azure-dns.com, .net, .org and .info).
In the registrar's panel (Registro.br, GoDaddy, etc.), replace the current DNS servers with Azure's 4 and save.
⚠️ Important: after delegation, the whole zone is managed on Azure DNS — recreate there any records that already existed (site, email, SPF). Propagation can take up to 72 hours.
Verification
In edrone: click Verify records — the status turns green (Verified) once it propagates.
In Azure: open the DNS Zone and check the record sets created.
External tools: dnschecker.org, mxtoolbox.com, whatsmydns.net.
What if you can't configure NS records?
Not every DNS provider lets you add NS records for subdomains. If that's your case, click I can't configure NS records in edrone's DNS configuration screen. This switches you to the alternative setup using standard DNS records (CNAME and TXT). You'll find the full guide in the article How to verify your domain if your provider does not support NS records.
Need more help?
If you have any further questions about configuring DNS on Azure DNS, please do not hesitate to contact us at hello@edrone.me