Weekly product update: Validate DNS records using the Domains API
A quick update detailing the DNS record validations going on in the Domains API in Beta. Read more –
We recently told you about our two newest APIs both in private beta: Domains and Webhooks. We’ve seen a lot of interest so far and gotten some good feedback. Thanks! If you want to try them yourself, just send an email to firstname.lastname@example.org with your Github handle and we’ll add you. This week’s product update–DNS record validation– is an improvement to the Domains API which makes it a lot more useful if you are building an application that gives your end-users the ability to white-label their own emails. Here’s how:
table of content
Validate DNS records using the Domains API
When you set up a domain in Mailgun, you’re given some DNS records that allow Mailgun to send and receive email on your behalf, and track clicks and opens. These records are displayed in the Domain detail page of your control panel.
With the new Domains API, these values are also available programmatically so that you can display the appropriate records to your clients directly through your application.
But what if you want to know if your customer has properly set up the records you provided them? No problem. Using the Domains API you can determine whether or not SPF, DKIM, CNAME and MX records are properly configured. When you use the Domains API to get information about a particular domain, we’ll return all DNS records, along with a status of each: valid or unknown. Valid means just what it sounds like, the DNS record is properly configured. Unknown means that something isn’t right. Maybe they mistyped it, or maybe it just hasn’t propagated yet. As you troubleshoot with your customer, you can check it again to make sure the records are valid before proceeding.
That’s it for this week. To those of you in the USA, we hope you had a happy 4th of July. Till next week!