Changing my hostname and nameservers (Newbie)

GregW

Verified User
Joined
Aug 6, 2019
Messages
28
Location
Australia
Hi all

I am wanting to change my hostname and nameservers, I have read this guide - https://forum.directadmin.com/threa...e-your-servers-hostname-in-directadmin.70371/

Which really helps me have some understanding on the process.

But before I do, as I am VERY new to this, how do I maintain access to DA if I make the changes. I currently access my DA via https://ns1.mydomain.com:2222/evo/.

If I change the hostname to server.mynewdomain.com and the nameservers to the same domain, ns1.mynewdomain.com and ns2.mynewdomain.com. Do I just re-access my DA using https://server.mynewdomain.com:2222/evo/?

I have created a user account for the mynewdomain.com, but do I need to create one for server.mynewdomain.com as well or as the only one?

I am worried I will lose my access to DA after I make the change and struggle to get it back and working.

As per the guide I will need to check server SSL to the new hostname, correct?

Thanks for your input
 
Yes — once `server.mynewdomain.com` resolves to this server, you should access DA at `https://server.mynewdomain.com:2222/evo/`.

You do not need a separate DirectAdmin User/domain for `server.mynewdomain.com`. Treat it as the machine hostname. Before changing anything, create/verify DNS records for `server`, `ns1`, and `ns2` (A records, plus AAAA only if IPv6 is actually configured). Because the nameservers are inside the same domain, also register/update their child nameserver/glue records at the registrar.

Keep the current DA session open during the change. As an emergency fallback, `https://server-ip:2222` should still reach DA, although the browser will show a certificate-name warning. Having SSH/provider-console access is sensible too.

Then change Admin Level → Admin Settings → Server's Hostname and allow about a minute for DA to restart. Set the new nameservers separately and update registrar delegation where required. Once the new hostname resolves publicly, use Server Manager → Server TLS Certificate to issue the hostname certificate. The old hostname should not be considered a permanent fallback after DNS/certificate changes.
 
You can access directadmin always via any domain on your server. So if mynewdomain.com is working then you can even just use https://mynewdomain.com:2222 to access DA. You don't even need the /evo/? behind it as it will put it there automatically.

So you could use that domain name, server.mynewdomain.com but also ns1 or ns2.mynewdomain.com of customerdomain.com for that matter.
As long as you provide your own credentials you will end up on the correct place in Directadmin.

If you use my manual and set a seperate hostname in DNS, be aware about the point of checking presence of the hostname in the /etc/virtual directory as written in the howto. Also if everything is changed and the old hostname is still in there you can remove it.
 
Back
Top