| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:how_to_create_a_domain [2024/11/08 12:57] – [Step 2: Choose configuration method] bk | en:how_to_create_a_domain [2025/02/27 14:54] (current) – bk |
|---|
| ====== How to create a domain? ====== | ====== How do I create a domain? ====== |
| |
| To use a domain in promio.connect as sender domain, you need to register it with your provider. \\ Add the domain under //Settings > Domains// as sender domain to generate and display the records to be entered at your provider for this domain. | To use a domain in promio.connect as a sender domain, you need to register it with your provider. \\ Add the domain under //Settings > Domains// as the sender domain to generate and display the records to be entered at your provider for this domain. |
| |
| <WRAP round info 80%> | <WRAP round info 80%> |
| By adding the domain in promio.connect, you do not buy it, but make it available for delivery. | By adding the domain in promio.connect, you do not buy it but make it available for delivery. |
| |
| By creating from addresses for the domain later, no mailbox is created in promio.connect with this address through which replies can be received. | By creating from addresses for the domain later, no mailbox is created in promio.connect with this address through which replies can be received. |
| We recommend sending newsletters with your own sender domain. A sender address that can immediately be associated with your company creates trust in the recipient and can have a positive effect on the open rate. | We recommend sending newsletters with your own sender domain. A sender address that can immediately be associated with your company creates trust in the recipient and can have a positive effect on the open rate. |
| |
| You should use a domain or subdomain that is used exclusively by promio.connect as sender. Multiple use of domains / subdomains may lead to incorrect delivery of emails. A sender domain should be accessible, belong to your own company and when the domain is accessed the company's website should be reached. This can also be a redirect. \\ If you want to use your main domain – the same one used for corporate communication – as sender domain, then you have to define a subdomain for this domain, which is reserved for use by promio.connect only. I.e. the recipients receive your newsletter e.g. from info@mail.yourCompanyDomain.com or info@newsletter.yourCompanyDomain.com | You should use a domain or subdomain that is used exclusively by promio.connect as the sender. Multiple uses of domains/subdomains may lead to incorrect delivery of emails. A sender domain should be accessible, belong to your own company, and when the domain is accessed, the company's website should be reached. This can also be a redirect. \\ If you want to use your main domain, then you have to define a subdomain for this domain, which is reserved for use by promio.connect only. I.e., the recipients receive your newsletter, e.g., from info@mail.yourCompanyDomain.com or info@newsletter.yourCompanyDomain.com. |
| |
| By clicking the green button on the bottom right you create a new domain. \\ {{:en:icon_create_domain.png?nolink&120}} | By clicking the green button on the bottom right, you create a new domain. \\ {{:en:icon_create_domain.png?nolink&120}} |
| |
| //Domain//: \\ Enter the preferred sender domain. The domain is used as sender domain for your mailings. | //Domain//: \\ Enter the preferred sender domain. The domain is used as the sender domain for your mailings. |
| |
| //Redirect URL//: \\ Enter a corresponding redirect URL. The redirect URL is used for link tracking within your mailings. | //Redirect URL//: \\ Enter a corresponding redirect URL. The redirect URL is used for link tracking within your mailings. |
| |
| |
| ==== Step 2: Choose configuration method ==== | ==== Step 2: Choose a configuration method ==== |
| |
| Choose the configuration method. If your sender domain is not a subdomain, only the //Advanced// method is possible. | Choose the configuration method. If your sender domain is not a subdomain, only the //Advanced// method is possible. |
| |
| //Simple//: Choose this method if your domain is a subdomain and is used exclusively for sending e-mails in promio.connect and is not already in use elsewhere (e.g. as a domain for a website). \\ | //Simple//: Choose this method if your domain is a subdomain and is used exclusively for sending emails in promio.connect and is not already in use elsewhere (e.g., as a domain for a website). \\ |
| //Advanced//: Choose this method if the sender domain is already in use as a domain for a website or you want to have full control over all DNS settings. | //Advanced//: Choose this method if the sender domain is already in use as a domain for a website or you want to have full control over all DNS settings. |
| |
| <WRAP round important 60%>There is also the configuration method //External//. | <WRAP round important 60%>There is also the configuration method //External//. |
| |
| Sending via the domain takes place externally via your infrastructure, e.g. via SMTP relay. No DNS records are required for the sender domain. Only the redirect domain and the reputation of the domain are checked. There is no bounce management by default. System-side redirects cannot be created for these domains. | Sending via the domain takes place externally via your infrastructure, e.g., via SMTP relay. No DNS records are required for the sender domain. Only the redirect domain and the reputation of the domain are checked. There is no bounce management by default. System-side redirects cannot be created for these domains. |
| |
| However, this must be configured by promio.net. If you are interested, please contact our support team via a ticket.</WRAP> | However, this method must be configured by promio.net. If you are interested, please contact our support team via a ticket.</WRAP> |
| ==== Step 3: Register domain ==== | ==== Step 3: Register domain ==== |
| |
| |
| |
| ==== Step 4: View required DNS records and register them with provider ==== | ==== Step 4: View required DNS records and register them with the provider ==== |
| |
| After registration, you will be taken to an overview that lists all DNS records to be done at the provider: | After registration, you will be taken to an overview that lists all DNS records to be done at the provider: |
| * //System settings//: \\ This setting is done automatically by promio.net. Note that the required changes will take about 24 hours AFTER the DNS records have been successfully validated. | * //System settings//: \\ This setting is done automatically by promio.net. Note that the required changes will take about 24 hours AFTER the DNS records have been successfully validated. |
| |
| * //CNAME - Sender domain//: \\ Only necessary with configuration method "Simple". \\ Add the CNAME specified under "Expected" to the DNS records of your new sender domain. \\ For verification purposes, you will see a comparison between the given entry and the one you may have already made. | * //CNAME - Sender domain//: \\ Only necessary with the configuration method “Simple”. \\ Add the CNAME specified under "Expected" to the DNS records of your new sender domain. \\ For verification purposes, you will see a comparison between the given entry and the one you may have already made. |
| | |
| * //DKIM//: \\ The usage of DKIM improves the deliverability of your newsletters and is obligatory for sending via promio.connect. \\ First create the required subdomain, and then add the TXT record (public key) specified under "Expected" to the DNS records of this subdomain. \\ For verification purposes, you will see a comparison between the given entry and the one you may have already made. | * //DKIM//: \\ The usage of DKIM improves the deliverability of your newsletters and is obligatory for sending via promio.connect. \\ First create the required subdomain, and then add the TXT record (public key) specified under "Expected" to the DNS records of this subdomain. \\ For verification purposes, you will see a comparison between the given entry and the one you may have already made. |
| |
| * //MX Records//: \\ Only necessary with configuration method "Advanced". \\ Add the servers listed under "Expected" as MX records to the DNS of your new sender domain. All of these records should have the same priority, e.g. 10. \\ For verification purposes, you will see a comparison between the given entries and the ones you may have already made. | * //MX Records//: \\ Only necessary with the configuration method "Advanced". \\ Add the servers listed under "Expected" as MX records to the DNS of your new sender domain. All of these records should have the same priority, e.g., 10. \\ For verification purposes, you will see a comparison between the given entries and the ones you may have already made. |
| |
| * //SPF//: \\ Only necessary with configuration method "Advanced". \\ Add the TXT record specified under "Expected" to the DNS records for your new sender domain. \\ For verification purposes, you will see a comparison between the given entry and the one you may have already made. \\ Usage of SPF improves the deliverability of your newsletters, especially in foreign ISPs. | * //SPF//: \\ Only necessary with configuration the method "Advanced". \\ Add the TXT record specified under “Expected” to the DNS records for your new sender domain. \\ For verification purposes, you will see a comparison between the given entry and the one you may have already made. \\ |
| | Usage of SPF improves the deliverability of your newsletters, especially in foreign ISPs. |
| |
| * //CNAME - Redirect URL//: \\ Enter the CNAME specified under "Expected" into the DNS records of your new redirect domain. \\ Also note that the sender domain cannot be used as redirect URL at the same time! \\ When the redirect domain was used since 2014 in promio.connect, an A-record might be active. Only in such exceptional cases may the redirect domain correspond to the sender domain. | * //CNAME - Redirect URL//: \\ Enter the CNAME specified under "Expected" into the DNS records of your new redirect domain. \\ Also note that the sender domain cannot be used as a redirect URL at the same time! \\ When the redirect domain was used since 2014 in promio.connect, an A-record might be active. Only in such exceptional cases may the redirect domain correspond to the sender domain. |
| |
| * //DMARC//: \\ Using DMARC is optional, so sending with this domain is also possible without using DMARC. \\ Add the TXT record specified under "Expected" to the DNS records of the shown subdomain to your DNS to optimize delivery speed and deliverability. \\ You may list multiple addresses comma-separated within the TXT record in the //mailto// - the address of sender domain should be listed first. | * //DMARC//: \\ Using DMARC is optional, so sending with this domain is also possible without using DMARC. \\ Add the TXT record specified under "Expected" to the DNS records of the shown subdomain to your DNS to optimize delivery speed and deliverability. \\ You may list multiple addresses comma-separated within the TXT record in the //mailto// - the address of the sender domain should be listed first. |
| |
| |
| Once the changes have been distributed, promio.connect returns an "OK" for complete and correct records. If an error occurs with one of the items, please correct the corresponding DNS record with the provider of your domain. | Once the changes have been distributed, promio.connect returns an "OK" for complete and correct records. If an error occurs with one of the items, please correct the corresponding DNS record with the provider of your domain. |
| |
| You can also check DNS records using online tools, e.g. [[https://mxtoolbox.com/SuperTool.aspx?run=toolpage&action=mx%3amydomain.com|MxToolBox]]. If you have questions, please contact our support team via ticket. | You can also check DNS records using online tools, e.g., [[https://mxtoolbox.com/SuperTool.aspx?run=toolpage&action=mx%3amydomain.com|MxToolBox]]. If you have questions, please contact our support team via ticket. |
| |
| |
| ===== Setup of a system side redirect ===== | ===== Setup of a system-side redirect ===== |
| |
| A system side redirect forwards all e-mails sent to addresses of your sender domain to the indicated target address - which is not visible to the responder. Thus - in contrast to the functionality of a reply-to address - e.g. all automatic replies or replies created by copying the from address and then opening a new e-mail are also forwarded. | A system-side redirect forwards all emails sent to addresses of your sender domain to the indicated target address, which is not visible to the responder. Thus, in contrast to the functionality of a reply-to address, e.g., all automatic replies or replies created by copying the from address and then opening a new email are also forwarded. |
| |
| By default, e-mails to the sender domain are ignored. You can activate forwarding of these e-mails to any e-mail address via the action "Edit system side redirect". Make sure that the entered e-mail address exists and that your company has access to the corresponding mailbox. | By default, emails to the sender domain are ignored. You can activate forwarding of these emails to any email address via the action “Edit system side redirect”. Make sure that the entered email address exists and that your company has access to the corresponding mailbox. |
| |
| Klick on the domain in section //Settings -> Domains//. Access this via the button at the top right. | Click on the domain in the section //Settings -> Domains//. Access this via the button at the top right. |
| |
| {{:en:settings_domains_systemside_redirect.png?nolink&200|}} | {{:en:settings_domains_systemside_redirect.png?nolink&200|}} |
| ===== Overview registered domains ===== | ===== Overview registered domains ===== |
| |
| Under //Settings > Domains// you will find an overview of all domains registered in promio.connect: | Under //Settings > Domains//, you will find an overview of all domains registered in promio.connect: |
| |
| {{:en:settings_domains_1.png?nolink&700|}} | {{:en:settings_domains_1.png?nolink&700|}} |
| | |
| In the //Status// column you can see whether the DNS entries at the provider of the domain are all valid. | In the //Status// column, you can see whether the DNS entries at the provider of the domain are all valid. |
| |
| * //Green icon//: DNS settings are correct and the domain can be used for delivery. | * //Green icon//: DNS settings are correct, and the domain can be used for delivery. |
| * //Yellow warning icon//: There are DNS records that should be updated. You can get further information in the detailed view of the domain. The domain can still be used for delivery. | * //Yellow warning icon//: There are DNS records that should be updated. You can get further information in the detailed view of the domain. The domain can still be used for delivery. |
| * // Red warning icon//: There are incorrect DNS entries. In the detailed view of the domain you get hints about which problems occur. The domain cannot be used for delivery. | * // Red warning icon//: There are incorrect DNS entries. In the detailed view of the domain, you get hints about which problems occur. The domain cannot be used for delivery. |
| |
| |
| {{tag>domains DKIM SPF DNS MX providers records redirects }} | {{tag>domains DKIM SPF DNS MX providers records redirects }} |
