castris
Verified User
At first I associated it with the fact that I am a novice, but I have been preparing my templates for different VPS deployments with Directadmin for two days and I have encountered the same problem everywhere.
The hostname change model server-Ip.IP.IP.IP.da.direct. does not work:
- Neither in `Dashboard >> Admin Settings >> Server Settings`
- Neither via shell: `hostnamectl set-hostname server.mydomain.com` The latter changes at the server level, but Directadmin continues to think of the other name.
This is what I have read.
Apart from what is known in Linux.
## Steps and details
- The server has a correct `myhostname.domain.tld`
- The server responds with `hostname -f` with `myhostname.domain.tld`
- The IP has a PTR that resolves to the same hostname.
- It has been restarted several times "just in case"
However, whenever we request a certificate with `cd /usr/local/directadmin/scripts && ./letsencrypt.sh request_single myhostname.domain.tld` the creation of `server-IP-XX-XX-XX.da.direct` appears.
I have performed a search on the server to locate the string `server-IP-XX-XX-XX` without result.
I am starting to feel annoyed, and lost.
Seriously, it cannot be that such a simple thing, destroys software that seems so beautiful.
## NOTE
The passage of time also takes its toll on the collection of information sources on certain subjects, and new documentation has the same defect that we all have who make software. We write for ourselves without taking into account that the reader may have knowledge, but what he is looking for is knowledge of the environment in which he is currently immersed.
The hostname change model server-Ip.IP.IP.IP.da.direct. does not work:
- Neither in `Dashboard >> Admin Settings >> Server Settings`
- Neither via shell: `hostnamectl set-hostname server.mydomain.com` The latter changes at the server level, but Directadmin continues to think of the other name.
This is what I have read.
Apart from what is known in Linux.
## Steps and details
- The server has a correct `myhostname.domain.tld`
- The server responds with `hostname -f` with `myhostname.domain.tld`
- The IP has a PTR that resolves to the same hostname.
- It has been restarted several times "just in case"
However, whenever we request a certificate with `cd /usr/local/directadmin/scripts && ./letsencrypt.sh request_single myhostname.domain.tld` the creation of `server-IP-XX-XX-XX.da.direct` appears.
I have performed a search on the server to locate the string `server-IP-XX-XX-XX` without result.
I am starting to feel annoyed, and lost.
Seriously, it cannot be that such a simple thing, destroys software that seems so beautiful.
## NOTE
The passage of time also takes its toll on the collection of information sources on certain subjects, and new documentation has the same defect that we all have who make software. We write for ourselves without taking into account that the reader may have knowledge, but what he is looking for is knowledge of the environment in which he is currently immersed.