Here's the situation.
We have a domain. Let's say it's example.domain
. There's a DNS server somewhere for this domain and there's a mail server for emails from/to this domain too. Now, there's a linux machine with ISPConfig on it on which I want to host sites (without email sending support) for home.example.domain
. So, I edit DNS zone files for domain example.domain on its DNS server to home.example.domain point to ISPConfig managed server. Ping/traceroute to home.example.domain works just fine pointing to the correct machine.
In ISPConfig you have to add new site and it's address by splitting domain and host part of address. So you can only enter home as host and example.domain as domain. This way example.domain gets on to local-host-names file for postfix. Do you know what that gives? You cannot send email to any address from example.domain (like email@example.com
) from any other account/domain that is hosted on ISPConfig machine because postfix thinks that example.domain is on local machine and tries to send it locally. The problem persists if you add www as host and home.example.domain as domain while adding new site - still you get home.example.domain and example.domain added to local-host-names file.
Is there some option to force ISPConfig not to add domain to local-host-names? Is there a correct method for adding subdomains as new sites without using www prefix/host?
And one more thing. I've added some site, it worked for a couple of days then I got rid of it from ISPConfig using www admin panel. Why local-host-names still got this domain in it? Why there's an entry in mysql table isp_isp_domain