DA in Debian10

P

pietrek

Verified User
Joined
Apr 19, 2021
Messages
9
Hello

I have installed DA on my debian10 system. The first thing I noticed is that BIND9 is not running at all. Should it be that way? It is installed but not running.
When I run it, there is a problem with name resolution.
Tell me what information should I send you from my configuration to verify it or maybe there is someone willing to help remotely?

Regards,
Peter
 
pietrek said:
Hello

I have installed DA on my debian10 system. The first thing I noticed is that BIND9 is not running at all. Should it be that way? It is installed but not running.
When I run it, there is a problem with name resolution.
Tell me what information should I send you from my configuration to verify it or maybe there is someone willing to help remotely?

Regards,
Peter
Click to expand...
If DirectAdmin is installed on an fresh server (So only OS install and nothing else.) then this is not a problem. I run Debian 10 myself but never heard of BIND9 so i think its not needed? or if DirectAdmin uses it then it will configure it as it needs it.
 
realcryptonight said:
If DirectAdmin is installed on an fresh server (So only OS install and nothing else.) then this is not a problem. I run Debian 10 myself but never heard of BIND9 so i think its not needed? or if DirectAdmin uses it then it will configure it as it needs it.
Click to expand...
I did a quick google and BIND9 is for DNS. But when i look at my running services its not listed. So i think everything is good.
 
As far as I know, bind is used on all DirectAdmin servers, so I'm pretty sure you have it. The process name/binary is called named. On our debian servers, we add the following line to /usr/local/directadmin/conf/directadmin.conf so that the correct service is started/stopped/restarted, you might need to do the same:

Code: 
named_service_override=bind9

What is the problem with name resolution you have when it's started?
 
kristian said:
As far as I know, bind is used on all DirectAdmin servers, so I'm pretty sure you have it. The process name/binary is called named. On our debian servers, we add the following line to /usr/local/directadmin/conf/directadmin.conf so that the correct service is started/stopped/restarted, you might need to do the same:

Code: 
named_service_override=bind9

What is the problem with name resolution you have when it's started?
Click to expand...
No as far as i know named is the default. And this support article also seems to agree.
 
The problem with resolving the name I wrote about:

Code: 
root@server:/home/pietrek# wget https://data.installatron.com/installatron-plugin-directadmin_latest_all.deb
--2021-04-20 20:44:05--  https://data.installatron.com/installatron-plugin-directadmin_latest_all.deb
Translacja data.installatron.com (data.installatron.com)... nieudane: Odwzorowanie nazwy jest chwilowo niemożliwe.
wget: nie udało się rozwiązać adresu hosta `data.installatron.com'
 
This error does not necessarily relate to whether or not your local Bind works. If it does relate, you should not use localhost as a resolver (as defined in /etc/resolv.conf or elsewhere depending on your OS), since you will potentially get the wrong response for domains you have defined locally. Depending on your bind config, recursive lookups will be rejected as well (this might be the case for you).

You should use some other resolver in your network (ask your hosting provider if you don't have your own), or public ones (e.g. 1.1.1.1, 1.0.0.1 (cloudflare), 8.8.8.8, 8.8.4.4 (google), 9.9.9.9 (quad9), etc).
 
You must log in or register to reply here.
Back
Top