I cannot for the life of me, disable da branded url

[rhiannon]

we have a domain, server-x.x.x.x.da.direct:2222 and I have done everything I can think of to disable the branded domain. We have it setup on a subdomain just fine but these domains at da.direct can be programmatically scanned and I want to reduce the attack surface. I have removed all certs, changed the hostname on the server, readded certs, not sure what do here. Please advise.

 

[johannes]

Thread '[How-To] Create or change your server's hostname in Directadmin'

Mar 21, 2024

This is a guide on how to create a correct FQDN hostname on a sever or VPS.
I created this newly here in this section, for easier reference and it's also easier to find.

There is also another method, but the method described here is another method which is also still very usable.

Before you install Directadmin you can already take care the correct hostname is used bij Directadmin.

The domain mydomain.com is used her as example and 192.168.0.1 as example server ip. Ofcourse replace all examples with the domain or hostname your are using. So don't use 192.168.0.1 in the real situation...

• Richard G
• Replies: 7
• Forum: How-To Guides

• 

 

[DrWizzle]

Don't forget if you're changing your hostname, make sure you set up an rDNS record at your host and also corresponding A / AAAA records. If you have more than 1 IP pointing to your server that you use, also make sure they have A and rDNS records, and create the /etc/virtual/helo_data file

nano /etc/virtual/helo_data #enter your ip addresses and FQDNs in this file.
chmod 644 /etc/virtual/helo_data #set correct file parameters
da build exim_conf #this will update exim conf file
da build exim # this will reset and restart exim with new config"

This will update the config files and really help EXIM with mail deliverability. If not you can run the risk of getting blacklisted on Spamhaus and the likes.
Also as said before, make sure your DKIM is enabled, and also consider putting a _DMARC TXT record in your DNS