1

Topic: Setting up a new subdomain

Hello,
I'm interested in setting up a new mail subdomain in our server, that is, I currently have a domain.com domain set up (and working for more than 1 year), and now I have the need to set up a new sales.domain.com subdomain. Do you have any documentation on how to set up this? I've already created the MX records. I haven't found anything on the docs about it.
Thanks in advance.
Best regards,

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.6 MARIADB edition.
- Linux/BSD distribution name and version: CentOS 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx):Apache
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Setting up a new subdomain

Is it mail domain name or web host domain name?

- For mail domain name, simply add this domain with the web admin panel (https://<server>/iredadmin), then make sure you have correct DNS records (A/MX/SPF/DKIM).

- For web host domain, you need to add a new Nginx config file under /etc/nginx/sites-available/, then create a symbol link of this new file to /etc/nginx/sites-enabled/, restart or reload Nginx service. FYI:
https://www.nginx.com/resources/wiki/st … er_blocks/

3

Re: Setting up a new subdomain

Thanks, I didn't realize that a new domain could be created with the web admin panel. It's working now.
Thanks again,

ZhangHuangbin wrote:

Is it mail domain name or web host domain name?

- For mail domain name, simply add this domain with the web admin panel (https://<server>/iredadmin), then make sure you have correct DNS records (A/MX/SPF/DKIM).

- For web host domain, you need to add a new Nginx config file under /etc/nginx/sites-available/, then create a symbol link of this new file to /etc/nginx/sites-enabled/, restart or reload Nginx service. FYI:
https://www.nginx.com/resources/wiki/st … er_blocks/