Hello,
I notice that users will get DirectAdmin messages with a link to the relevant message, however at every time it will use their main domain in the URL followed by port 2222. It would be better that this were the server hostname, since it's really the only domain name that is SSL secured with a valid certificate.
I cannot use the variable |HOSTNAME| in the custom templates for message_user.txt and message_tech.txt. The only option is to type in the current hostname manually, which I would like to avoid since I'll certainly forget to alter these files if I ever change the hostname...
Couldn't this be easily added into the next DirAdmin version? Allowing the usage of the token |HOSTNAME| for message templates.
Likewise for the named.db template, I'd like to be able to use the |HOSTNAME| token to put it in the SOA record. It seems that there is no clear list of tokens usable per template file, nor an easy way to generate such a list... I cannot risk using the |HOSTNAME| token in the named.db template, since it could break my DNS as well as my backup servers which use AXFR and would take over the changes.
Kenneth
I notice that users will get DirectAdmin messages with a link to the relevant message, however at every time it will use their main domain in the URL followed by port 2222. It would be better that this were the server hostname, since it's really the only domain name that is SSL secured with a valid certificate.
I cannot use the variable |HOSTNAME| in the custom templates for message_user.txt and message_tech.txt. The only option is to type in the current hostname manually, which I would like to avoid since I'll certainly forget to alter these files if I ever change the hostname...
Couldn't this be easily added into the next DirAdmin version? Allowing the usage of the token |HOSTNAME| for message templates.
Likewise for the named.db template, I'd like to be able to use the |HOSTNAME| token to put it in the SOA record. It seems that there is no clear list of tokens usable per template file, nor an easy way to generate such a list... I cannot risk using the |HOSTNAME| token in the named.db template, since it could break my DNS as well as my backup servers which use AXFR and would take over the changes.
Kenneth
Last edited:
