[Solved] Bind doesn't work anymore | Named is Bind

Albert

Verified User
Joined
Oct 25, 2019
Messages
57
netstat -lnp | grep 53

Below the result
~# netstat -lnp | grep 53
Code:
tcp        0      0 91.121.45.207:53        0.0.0.0:*               LISTEN      2908/named
tcp        0      0 91.121.37.27:53         0.0.0.0:*               LISTEN      2908/named
tcp        0      0 87.98.175.227:53        0.0.0.0:*               LISTEN      2908/named
tcp        0      0 87.98.170.230:53        0.0.0.0:*               LISTEN      2908/named
tcp        0      0 87.98.169.140:53        0.0.0.0:*               LISTEN      2908/named
tcp        0      0 87.98.169.132:53        0.0.0.0:*               LISTEN      2908/named
tcp        0      0 87.98.160.153:53        0.0.0.0:*               LISTEN      2908/named
tcp        0      0 51.38.250.175:53        0.0.0.0:*               LISTEN      2908/named
tcp        0      0 51.38.215.47:53         0.0.0.0:*               LISTEN      2908/named
tcp        0      0 51.38.215.43:53         0.0.0.0:*               LISTEN      2908/named
tcp        0      0 51.68.71.112:53         0.0.0.0:*               LISTEN      2908/named
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2908/named
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      2908/named
tcp6       0      0 :::53                   :::*                    LISTEN      2908/named
tcp6       0      0 ::1:953                 :::*                    LISTEN      2908/named
udp        0      0 87.98.160.153:123       0.0.0.0:*                           441/ntpd
udp        0      0 91.121.45.207:53        0.0.0.0:*                           2908/named
udp        0      0 91.121.37.27:53         0.0.0.0:*                           2908/named
udp        0      0 87.98.175.227:53        0.0.0.0:*                           2908/named
udp        0      0 87.98.170.230:53        0.0.0.0:*                           2908/named
udp        0      0 87.98.169.140:53        0.0.0.0:*                           2908/named
udp        0      0 87.98.169.132:53        0.0.0.0:*                           2908/named
udp        0      0 87.98.160.153:53        0.0.0.0:*                           2908/named
udp        0      0 51.38.250.175:53        0.0.0.0:*                           2908/named
udp        0      0 51.38.215.47:53         0.0.0.0:*                           2908/named
udp        0      0 51.38.215.43:53         0.0.0.0:*                           2908/named
udp        0      0 51.68.71.112:53         0.0.0.0:*                           2908/named
udp        0      0 127.0.0.1:53            0.0.0.0:*                           2908/named
udp6       0      0 :::53                   :::*                                2908/named
unix  2      [ ACC ]     STREAM     LISTENING     531755   439/dovecot          /var/run/dovecot/stats-reader
unix  2      [ ACC ]     STREAM     LISTENING     531757   439/dovecot          /var/run/dovecot/stats-writer
unix  2      [ ACC ]     STREAM     LISTENING     531759   439/dovecot          /var/run/dovecot/replicator
unix  2      [ ACC ]     STREAM     LISTENING     531761   439/dovecot          /var/run/dovecot/replication-notify
unix  2      [ ACC ]     STREAM     LISTENING     531764   439/dovecot          /var/run/dovecot/login/pop3
unix  2      [ ACC ]     STREAM     LISTENING     531766   439/dovecot          /var/run/dovecot/old-stats
unix  2      [ ACC ]     STREAM     LISTENING     531770   439/dovecot          /var/run/dovecot/log-errors
unix  2      [ ACC ]     STREAM     LISTENING     531772   439/dovecot          /var/run/dovecot/lmtp
unix  2      [ ACC ]     STREAM     LISTENING     531774   439/dovecot          /var/run/dovecot/lmtp-client
unix  2      [ ACC ]     STREAM     LISTENING     531776   439/dovecot          /var/run/dovecot/ipc
unix  2      [ ACC ]     STREAM     LISTENING     531778   439/dovecot          /var/run/dovecot/login/ipc-proxy
unix  2      [ ACC ]     STREAM     LISTENING     531780   439/dovecot          /var/run/dovecot/indexer-worker
unix  2      [ ACC ]     STREAM     LISTENING     531782   439/dovecot          /var/run/dovecot/indexer
unix  2      [ ACC ]     STREAM     LISTENING     531784   439/dovecot          /var/run/dovecot/login/imap
unix  2      [ ACC ]     STREAM     LISTENING     531786   439/dovecot          /var/run/dovecot/imap-master
unix  2      [ ACC ]     STREAM     LISTENING     531788   439/dovecot          /var/run/dovecot/imap-urlauth-worker
unix  2      [ ACC ]     STREAM     LISTENING     531790   439/dovecot          /var/run/dovecot/token-login/imap-urlauth
unix  2      [ ACC ]     STREAM     LISTENING     531792   439/dovecot          /var/run/dovecot/imap-urlauth
unix  2      [ ACC ]     STREAM     LISTENING     531794   439/dovecot          /var/run/dovecot/imap-hibernate
unix  2      [ ACC ]     STREAM     LISTENING     531796   439/dovecot          /var/run/dovecot/doveadm-server
unix  2      [ ACC ]     STREAM     LISTENING     531798   439/dovecot          /var/run/dovecot/dns-client
unix  2      [ ACC ]     STREAM     LISTENING     531800   439/dovecot          /var/run/dovecot/login/dns-client
unix  2      [ ACC ]     STREAM     LISTENING     531802   439/dovecot          /var/run/dovecot/director-admin
unix  2      [ ACC ]     STREAM     LISTENING     531804   439/dovecot          /var/run/dovecot/dict
unix  2      [ ACC ]     STREAM     LISTENING     531806   439/dovecot          /var/run/dovecot/dict-async
unix  2      [ ACC ]     STREAM     LISTENING     531808   439/dovecot          /var/run/dovecot/config
unix  2      [ ACC ]     STREAM     LISTENING     531810   439/dovecot          /var/run/dovecot/login/login
unix  2      [ ACC ]     STREAM     LISTENING     531812   439/dovecot          /var/run/dovecot/token-login/tokenlogin
unix  2      [ ACC ]     STREAM     LISTENING     531814   439/dovecot          /var/run/dovecot/auth-login
unix  2      [ ACC ]     STREAM     LISTENING     531816   439/dovecot          /var/run/dovecot/auth-client
unix  2      [ ACC ]     STREAM     LISTENING     531818   439/dovecot          /var/run/dovecot/auth-userdb
unix  2      [ ACC ]     STREAM     LISTENING     531820   439/dovecot          /var/run/dovecot/auth-master
unix  2      [ ACC ]     STREAM     LISTENING     531822   439/dovecot          /var/run/dovecot/auth-worker
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
9,616
Location
LT, EU
So, you have named started there. "ps auxwf | grep named" will show you when was it started. Just use general linux commands to kill the service and start it again, if systemd error is the only problem :) (as the service is up)
 

Albert

Verified User
Joined
Oct 25, 2019
Messages
57
~# ps auxwf | grep named
Code:
root      3352  0.0  0.0   6144   888 pts/0    S+   11:26   0:00          \_ grep named
bind      2908  0.0  1.4 165668 29032 ?        Ssl  May24   0:05 /usr/sbin/named -u bind

will show you when was it started

I know already, it started when I have updated directAdmin, since I spent more than 4 hours on this problem.

And now do you suggest to keep BIND failed ?
Code:
/etc/init.d/bind9 restart
[....] Restarting bind9 (via systemctl): bind9.serviceJob for bind9.service failed because the control process exited with error code.
See "systemctl status bind9.service" and "journalctl -xe" for details.
 failed!

I misunderstood ? or you are going to tell the process with the command line to avoid or repare this BUG from DirectAdmin ?

This is will help other people in the same time, you are not going to lose your time even if it's done for mine.

Thanks
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
9,616
Location
LT, EU
~# ps auxwf | grep named
Code:
root      3352  0.0  0.0   6144   888 pts/0    S+   11:26   0:00          \_ grep named
bind      2908  0.0  1.4 165668 29032 ?        Ssl  May24   0:05 /usr/sbin/named -u bind



I know already, it started when I have updated directAdmin, since I spent more than 4 hours on this problem.

And now do you suggest to keep BIND failed ?
Code:
/etc/init.d/bind9 restart
[....] Restarting bind9 (via systemctl): bind9.serviceJob for bind9.service failed because the control process exited with error code.
See "systemctl status bind9.service" and "journalctl -xe" for details.
failed!

I misunderstood ? or you are going to tell the process with the command line to avoid or repare this BUG from DirectAdmin ?

This is will help other people in the same time, you are not going to lose your time even if it's done for mine.

Thanks

1) it is running, not failed, and is responding to dns queries
2) you may kill the process and start it using systemctl then
3) I’d suggest checking if your OS matches the one set in the license
 

Albert

Verified User
Joined
Oct 25, 2019
Messages
57
/etc/init.d/bind9 restart
Code:
[....] Restarting bind9 (via systemctl): bind9.serviceJob for bind9.service failed because the control process exited with error code.
See "systemctl status bind9.service" and "journalctl -xe" for details.
failed!
I saw named is running, because all websites hosted are working well
But keep BIND Failed as above is not the right way to do even if named is working.

2) you may kill the process and start it using systemctl then
Kill named ? systemctl ?
Please give the command line, you are an expert, the basic things for you are not always easy for other...

3) I’d suggest checking if your OS matches the one set in the license
Debian 10, everything was working well until the last update of DirectAdmin a few days ago
 
Last edited:

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
9,616
Location
LT, EU
How comes you have /etc/init.d/bind9 ? I think you have systemd=0 in directadmin.conf ? Was it an upgraded machine from debian7?

Kill command is just:
kill -9 2908

I will repeat: it is not a bug of DA, not sure why you‘re trying to say this since the beginning :)
 

Albert

Verified User
Joined
Oct 25, 2019
Messages
57
How comes you have /etc/init.d/bind9 ? I think you have systemd=0 in directadmin.conf ? Was it an upgraded machine from debian7?

In /usr/local/directadmin/conf/directadmin.conf I do not have any "systemd=" that's Ok or something is wrong ?
I started with debian 10 and fresh install of DirectAdmin and Debian 10

Kill command is just:
kill -9 2908
Yes (y) after this command and "/etc/init.d/bind9 restart" BIND is running
~# /etc/init.d/bind9 restart
Code:
[ ok ] Restarting bind9 (via systemctl): bind9.service.

BUT if I restart the server, the problem is still the same and I need to follow the same process described above to be able to start BIND.

I will repeat: it is not a bug of DA, not sure why you‘re trying to say this since the beginning
I just report you the real the facts and problems, you are an expert, if you are saying DA is not responsible after an update even if it's was working perfectly before this update, I do not refuse to believe you... even it's quite hard to believe it ;)

And just to report one more things, since this update, that's not possible to make any action on "Named" from Admin Tools => Service Monitor
from DA interface http://IP:2222/admin/services

screenshot.2020-05-25 (3).jpg
Even if BIND is running
~# systemctl status bind9.service
Code:
● bind9.service - BIND Domain Name Server
   Loaded: loaded (/lib/systemd/system/bind9.service; disabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-05-25 16:17:47 CEST; 12s ago

DirectAdmin lost the control on the services of my VPS after one update ? or everything is my fault even if I have done only an update of DA ;)

But just to show you that I want to be honnest, this page describe a similar problem with Debian Fault

But DA should be MAGIC and should be one panel server to avoid this sort of problems and do not use command line, no ?
That's not like that DA is sold on your main home page ? :geek:
 
Last edited:

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
9,616
Location
LT, EU
Sorry, but I will not comment the questions. In short - personal license comes with community support only, that's the term you're agreeing to, when purchasing a license. The issue is - you're doing actions with bind9, while the service started was named "named". https://www.directadmin.com/features.php?id=2220.
 

Albert

Verified User
Joined
Oct 25, 2019
Messages
57
personal license comes with community support only
Yes I fully agree when the user want customized something or have done wrong changes and wrong things.

This long tread and many hours spent are apparently just because of the name used "named" instead of "Bind"
service named status = OK
service bind9 status = failed

I do not feel responsible for that, even if apparently I am in charge to solve this strange thing manually and insert code line in DA.

Fortunately you gave me a great help, and I would like to say THANKS

I made this change as you recommended me in /usr/local/directadmin/conf/directadmin.conf
Add => named_service_override=bind9
But DirectAdmin do not override, this is not working (I restarted the server)
 
Top