Setting up webmail.domain.com as default for new domains.

Enter Your Query:

Use '%' for wildcards and quotes for "exact phrases"

Setting up webmail.domain.com as default for new domains.

Last Modified: Oct 23, 2019, 9:33 pm

1) We'll need to add a webmail.* VirtualHost to each domain. We can make use of a feature that let's us globally specify CUSTOM# tokens, without altering the original templates.
Create the file

/usr/local/directadmin/data/templates/custom/virtual_host2.conf.CUSTOM.4.post

and add the code

taking note that we *start* the code with the closing </VirtualHost> because the CUSTOM4 token is before the trailing VH in the virtual_host2.conf template.

The above is for port http:80, but similar code can be used in:

/usr/local/directadmin/data/templates/custom/virtual_host2_secure.conf.CUSTOM.4.post

if you want it for https on the domain, you'd add:

2) Then run

echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d

to rewrite the httpd.conf files.

3) You'll also need to setup the dns portition.

cd /usr/local/directadmin/data/templates
cp dns_a.conf custom
cd custom
perl -pi -e "s/^smtp=\\|IP\\|\n/smtp=\\|IP\\|\nwebmail=\\|IP\\|\n/" dns_a.conf

This will setup the webmail A record for new dns zones. For existing dns zones, you'll have to manually add the webmail A record to point to the domains IP.

Related Helpfiles

Using a custom VirtualHost template

Running DirectAdmin through apache on port 80

Setting up webmail.domain.com with Nginx

Setting up webmail.domain.com with nginx/apache proxy