In this article, you will learn how to make the DNS configuration needed for good deliverability and to meet the authentication requirements of email providers.
We will split this into two steps: first you configure the record on your edrone platform, and then you add that record on AWS Route 53.
Step 1 - Configuring your DNS records in edrone
Go to SETTINGS > SENDING DOMAIN > CONFIGURE DNS RECORDS, then click Go to DNS configuration.
By default, edrone recommends NS records for your subdomain - you no longer need to add SparkPost/EmailLabs DKIM, SPF, and DMARC entries separately.
Always copy the values straight from your edrone panel (they are unique to your account) - never type them from memory. Paste them exactly, with no extra spaces.
To verify, click Verify records in edrone. The status turns green once DNS propagates.
Tip: propagation can take from a few minutes up to 72 hours, though Route 53 NS propagation is usually just a few hours. You can also check propagation externally with dnschecker.org, mxtoolbox.com, or whatsmydns.net.
Step 2 - Adding edrone NS record on AWS Route 53
Before you add edrone record, check which of the two scenarios applies to you.
A) Domain registered elsewhere, using Route 53 only for DNS (most common)
Create the hosted zone: in the AWS console, go to Route 53 > Hosted zones > Create hosted zone. Enter the domain exactly as registered, choose Public hosted zone, and create it.
Copy the 4 name servers Route 53 generates (each one starts with "ns-").
Update the NS records at your registrar: log in where the domain is registered, find the DNS servers/name servers section, replace them with Route 53 four, and save.
Important: every domain gets its own unique set of 4 name servers - never reuse another domain. NS propagation can take up to 72 hours (usually just a few).
B) Domain bought directly in Route 53
AWS already set up the hosted zone and NS automatically - skip straight to adding the record below.
Now add edrone record to the hosted zone:
Inside the hosted zone, click Create record.
For Record name, enter the subdomain edrone gave you (leave it blank only for root-level records - not typical for edrone subdomain setup).
For Record type, select NS (Route 53 supports NS records for subdomain delegation, same as any DNS host - this is the type to use for edrone recommended records; standard Route 53 record types also include A, CNAME, TXT, and MX, for other unrelated needs).
For Value, paste the NS values shown by edrone, one per line, then click Create records.
Tip: for any third-party verification record (e.g. DKIM-style), use exactly the record name the platform provides - do not add extra underscores or text. Records only take effect once NS has propagated.
What if my DNS provider does not support NS records
Route 53 supports NS records, so you usually will not run into this - it is a rare edge case. If your setup does not allow it, click the I can not configure NS records button inside the edrone DNS configuration dialog. You will switch to an alternative configuration using standard records, such as CNAME and TXT. If your provider starts supporting NS records later, you can always switch back by clicking Use recommended records.
You can find the full walkthrough in the article How to verify your domain if your provider does not support NS records.
Further reference
You can find AWS official documentation on creating a hosted zone here: Creating a public hosted zone (AWS Route 53 Developer Guide).
Need more help?
If you have any further questions about DNS configuration, please do not hesitate to contact us at hello@edrone.me