Cannot login to DirectAdmin with default Port

[icy23]

Hi all, I removed the www A name record last week. But now I can't access DirectAdmin with default Port. It shows DNS_PROBE_FINISHED_NXDOMAIN.

Any idea on how to fix this problem? Thank you.

 

[Richard G]

Why did you remove the www A record?
Did you already try putting it back?

 

[icy23]

I have to connect the e-commerce platform. They told me to manage the DNS field by adding CNAME and remove the www A record.
So how can I log into the DirectAdmin control panel now?

Why did you remove the www A record?
Did you already try putting it back?

 

[Richard G]

So the CNAME is pointing to your e-commerce platform, which is not www.yourdomain.com if I understand correctly.
I presume you did this on your domain name and not on the hostname record.

Normally this shouldn't matter and you still should be able to login via https://yourdomain.com:2222 unless there is a redirect present somewhere.
As alternative you can login using any other domain on the server for example https://otherdomain.com:2222 using your own credentials.

Or like earlier was done, try via the hostname like:
https://server.domain.com:2222 which should also work.

If these don't work then something else is wrong. However, in that case I wonder exactly where that A record was removed.

 

[BillyS]

If you are trying to access the site via windows, you can change your hosts file. It should be here:

C:\Windows\System32\Drivers\etc\hosts

Then you can add a line item to this file (edit as administrator). For example, the IP address of your domain, followed by the domain name.

192.168.1.1 yourdomain.com

Then you should be able to log in as

yourdomain.com:2222

 

[icy23]

The problem is solved. Thanks very much.

So the CNAME is pointing to your e-commerce platform, which is not www.yourdomain.com if I understand correctly.
I presume you did this on your domain name and not on the hostname record.

Normally this shouldn't matter and you still should be able to login via https://yourdomain.com:2222 unless there is a redirect present somewhere.
As alternative you can login using any other domain on the server for example https://otherdomain.com:2222 using your own credentials.

Or like earlier was done, try via the hostname like:
https://server.domain.com:2222 which should also work.

If these don't work then something else is wrong. However, in that case I wonder exactly where that A record was removed.