How to change Direct Admin Hostname, the proper way.

taker18

Verified User
Joined
Oct 18, 2021
Messages
141
Location
USA
Hello
I want to change the hostname
to Changing on the Admin Level > Administrator Settings > Server's Hostname
update NS1 and NS2 and save>
- on the Namecheap registrar I updated the hostname server NS1 and NS2 including the IP address
- the domain is configured on Cloudflare DNS

Now what else needs to be done. am I missing something else
Thank you
 
Little good update
I changed the Hostname successfully and added the NS1 and NS2 as hostname at Namecheap as private name server

Eventually, I was able to assign mydomain.com to be access DA instead of the IP ( yes this how i used signing to DA panel all the time IP:2222) only till now.
but now the domain is not secure no any SSL Certificate, and i checked

Automated SSL Certificates Information​


the hostname domain is not there should I assign and click the manual trigger. so far so good for me. the SSL is most be easier to handle I am sure.
this domain is using DA DNS, not Cloudflare, like all my other emails.
so far success, there is any more things that needs to be done, I appreciate the help from you all
 
but now the domain is not secure no any SSL Certificate, and i checked
The domain or the hostname? If you checked the Automated SSL Certificates, it will be installed for newly added domains, it might only still be made for the current domain, you should re-check a day later.

As for the hostname, if you want SSL on there, you need to run the manually command via SSH to do that.
Code:
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single `hostname` 4096
or
Code:
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single server.domain.com 4096
if your hostname is server.domain.com so replace by the correct value.
 
The domain or the hostname? If you checked the Automated SSL Certificates, it will be installed for newly added domains, it might only still be made for the current domain, you should re-check a day later.

As for the hostname, if you want SSL on there, you need to run the manually command via SSH to do that.
Code:
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single `hostname` 4096
or
Code:
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single server.domain.com 4096
if your hostname is server.domain.com so replace by the correct value.
Thank you @Richard G but I got an Error


server.domain.com was skipped due to unreachable http://server.domain.com/.well-known/acme-challenge/ file.
No domains pointing to this server to generate the certificate for.

DO I need to try this?
 
did you replaced server.domain.com with your server details ? if yes check your A record for your hostname

Yes A record server for hostname DNS
and the www. server also just add it a minute ago, does maybe need to be propagate still? not sure
I still have the old server A record and WWW.server on the old Hostname DNS, not sure if I delete it or not.
but anyway yes the server A record is there and WWW.server A record all there
Qustion? DO I need to create a subdomain server.domain.com (hostname)

Thank you Untitled.jpg
 
when I check whatsmydns for server.domain.com is not propagating whats so ever. but the domain.com is serving fine has SSL and great.
something I am dong wrong
OS Ubuntu
LiteSpeed server

the Hostname; server.domain.com
I am able to access DA from domain.com:2222, but just not SSL secure
ohh one more thing not sure if it helps Glue record on LEAFdns.com is showing the old NS1.oldhostname.com and NS2.oldhostname.com
I already deleted them few minutes ago but still around when i check
Thank you for help in advance
????
 
hello everyone
1- the same issue when I am trying to create SSL for server.domain.com, but the server.domain.com is not even

This site can’t be reached​

Check if there is a typo in server.domain.com.
DNS_PROBE_FINISHED_NXDOMAIN
1- server.domain.com is not propagating, while my hostname and nameserver are the same: server.newdomian.com

Question: what is the right way to access DA and make sure everything working properly? is it domain.com:2222 or server.domain.com:2222?
so far I am able to access the DA panel with http://domain.com:2222/
 
Last edited:
Normally you can access both ways, but easiest is just to use the last one so https://domain.com:2222 (or without the s if ssl is not working).
But you need that hostname anyway.

Just create the hostname as a seperate domain.
So as admin, click the "create domain" button and then use server.domain.com and things should be fine.

You also need to check if your OS uses the correct hostname now in /etc/hosts en /etc/hostname and for e-mail you need to create your PTR record with Hetzner to point to your hostname.

You are now using your own nameservers as I see, which is not the best way with only 1 ip, but it makes things easier to manage.

If you want I can have a look for you and fix things on your server, you can send me a pm then. I don't have lots of time today, but this probably won't take a lot of time. Just an offer, for free, but you're free to take it or not.
 
Last edited:
Fixed.

Most important cause of the problem was that the hostname record was corrupted somehow, it gave a read error on the named database file.
So after deleting the record and creating a new one and testing it, the rest of the issues were also more easy to solve.
 
Back
Top