The process of domain delegation gives Mapp the right to use your subdomain to send email. This step allows us to create the necessary DNS records to send email on your behalf.
Domain delegation is part of the onboarding process. This step is necessary before you can send emails with Engage.
Domain delegation does not give Mapp access to your primary domain. Mapp can only use the special subdomain that you create and designate for email marketing.
For branding purposes, Mapp recommends that you create a subdomain from your existing brand's domain. However, you can also set up a new domain.
Example
Your primary domain name is travelagency.com.
You create the subdomain news.travelagency.com.
When you delegate the subdomain to Mapp, Mapp can send emails from newsletter@news.travelagency.com (for example).
The subdomain you delegate must be a "real" subdomain, which means it has to be a sub-zone. An A (alias) or CNAME record is not sufficient.
You may have other A records with the same name. In this case, you either need to change the subdomain or delete the previous entry
Procedure
Determine the domain or subdomain you want to delegate (example: email.client.com). Ask your company IT department to set up this subdomain. If necessary, someone from Mapp can talk with your IT contact and discuss the request.
For each subdomain you plan to use to send emails with Engage, delegate each subdomain to the nameservers listed below. Delegation means that you create NS records for the new subdomain. Use the following nameservers:
ns1.shortest-route.com
ns2.shortest-route.de
ns3.shortest-route.com
Example 1:
subdomain
IN NS
ns1.shortest-route.com
subdomain
IN NS
ns2.shortest-route.de
subdomain
IN NS
ns3.shortest-route.com
Example 2:
subdomain
IN NS
ns1.shortest-route.com
IN NS
ns2.shortest-route.de
IN NS
ns3.shortest-route.com
Each record requires the period (".") at the end.
No additional entries are required. Everything else is done on the Engage nameservers.
Confirm that the subdomain is delegated correctly to Mapp.
