How to Fix Problems in Receiving/Sending Emails While Using CDN Services
A simple way of using the CDN system is to change the Domain Name Server (NS or Agent) to CDN NSs. Thereupon, ArvanCloud will respond to all the received requests of the domain's DNS. A website administrator can handle the DNS settings of the website via the ArvanCloud user panel.
To access these settings:
- Go to: CDN > Select the intended domain
- Click on DNS Records
It would be possible to define different subdomains in the DNS records section, activate/deactivate the Cloud icon and determine which subdomains' traffic will pass through the Cloud and which ones will be sent to the specified address directly.
CDN is used to accelerate web content delivery, and it can only pass content on HTTP and HTTPS protocols (Ports 80 and 443). Besides its web content, a website can have different services such as "Email Service," "File Transfer Protocol Service (FTP)," and other related ones.
How to Troubleshoot Problems in Receiving and Sending Email
A common problem some domains may encounter after transferring and using a CDN is the email service issues. However, it can be resolved.
While transferring or right after transferring the domain to ArvanCloud's content delivery network, check if the services "except for web content (HTTP and HTTPS traffics)," defined as "Domain Name" or "Subdomain," are directly pointing out to the server and the Cloud icon is deactivated.
The Email receiving/sending problems normally happen because the domain's MX records setting is incorrect. Go to the DNS settings on the ArvanCloud's panel, edit the details, and adjust the correct settings.
The MX record of each domain indicates the IP of a server assigned to manage the emails. For instance, the test.com domain's Mx record indicates which server is responsible for receiving/sending *@test.com emails. Since an MX record value cannot be directly equated to an IP address, it is essential to create an A record and then adjust the MX record to point out to that A record.
The image below is an example of a correct DNS setting for an Email service.
In this setting, the A record's Cloud icon is inactive and gray and points out to mail.test.com's subdomain.
If there is more than one server assigned as the receiving/sending email service, prioritize which server will act as the main receiving/sending email service and which one supports the other.
While using an external agent like Gmail or Zoho mail, there is no need to define A record; add the information to the user panel:
For using File Transfer Protocol (FTP) and other similar services, create a new subdomain (such as ftp.test.com), and deactivate their Cloud icon.
For other services in which it is obligated to use a "name" to function (like FTP), use the "IP address" instead of a name in the connecting software.