Bind not answering

ok I have run Ispconfig for a long time never had any real issuses
not an expert by any means

so my issuse is that I get no response from my server via DNS look up unless I manually start the named service
I thought named was not needed on Debian any more
anyway this is a brand new fresh install on a fresh debian 11 VM done with the auto installer
with out starting named I get
;; connection timed out; no servers could be reached

but I get a proper responce when I start it
which means at least ISPconfig is setting up the zones properly and the config files
and this is likely something simple as a result of debian 11


here is the output from me trying to set named to start on boot

Code:

root@ns1:/etc/init.d# update-rc.d named defaults
insserv: warning: current start runlevel(s) (empty) of script `named' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `named' overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `named' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `named' overrides LSB defaults (0 1 6).
insserv: script bind9: service bind9 already provided!

Code:

##### SERVER #####
IP-address (as per hostname): ***.***.***.***
[WARN] could not determine server's ip address by ifconfig
[INFO] OS version is Debian GNU/Linux 11 (bullseye)

[INFO] uptime:  14:19:46 up 16:32,  1 user,  load average: 0.01, 0.21, 0.32

[INFO] memory:
               total        used        free      shared  buff/cache   available
Mem:           1.0Gi       317Mi       156Mi        19Mi       549Mi       686Mi
Swap:          1.0Gi       202Mi       821Mi

[INFO] ISPConfig is installed.

##### ISPCONFIG #####
ISPConfig version is 3.2.8p1


##### VERSION CHECK #####

 

no your totally right but while having Bind running I have to manually start Named
to get it to answer in DNS requests just wondering what could cause this everything works as expected when I manually start Named but as I understand it I shouldn't need to start Named on Debian with bind9 the bind service should already be doing that

 

dkim=temperror ("DNS error when getting key")

there is for sure some DNS issue could it be that warning that the autoinstall script could not find my ip
and I need to configure Bind with my static ip some where corrently looking in config files

 

If you suspect name service error, my signature has link to DNS tutorial, which has troubleshooting instructions.

 

while this does not solve my Issue its good info and I will use the reverse dns stuff see if I can get my own setup
I think it is a resolver issue I am not a 100% sure what it is to be honest but I have 2 identical VPS setup and they both have the exact same problem

 

heres is a snip from the status of named

Code:

● named.service - BIND Domain Name Server
     Loaded: loaded (/lib/systemd/system/named.service; disabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-09-11 14:32:13 PDT; 2 days ago
       Docs: man:named(8)
   Main PID: 236741 (named)
      Tasks: 6 (limit: 19660)
     Memory: 12.9M
     CGroup: /system.slice/named.service
             └─236741 /usr/sbin/named -f -u bind

Sep 13 23:33:02 ns1.domian.ca named[236741]: network unreachable resolving 'com/DS/IN': 2001:500:200::b#53
Sep 13 23:33:02 ns1.domian.ca named[236741]: network unreachable resolving 'com/DS/IN': 2001:500:12::d0d#53
Sep 13 23:33:02 ns1.domian.ca named[236741]: network unreachable resolving 'com/DS/IN': 2001:503:ba3e::2:30#53
Sep 13 23:33:02 ns1.domian.ca named[236741]: validating com/DS: no valid signature found
Sep 13 23:33:02 ns1.domian.ca named[236741]: no valid RRSIG resolving 'com/DS/IN': 192.58.128.30#53
Sep 13 23:33:02 ns1.domian.ca named[236741]: validating com/DS: no valid signature found
Sep 13 23:33:02 ns1.domian.ca named[236741]: no valid RRSIG resolving 'com/DS/IN': 193.0.14.129#53

and from bind9.service

Code:

● bind9.service - LSB: Start and stop bind9
     Loaded: loaded (/etc/init.d/bind9; generated)
     Active: active (exited) since Sun 2022-09-11 14:33:33 PDT; 2 days ago
       Docs: man:systemd-sysv-generator(8)
    Process: 236787 ExecStart=/etc/init.d/bind9 start (code=exited, status=0/SUCCESS)

Sep 11 14:33:33 ns1.domian.ca systemd[1]: Starting LSB: Start and stop bind9...
Sep 11 14:33:33 ns1.domian.ca systemd[1]: Started LSB: Start and stop bind9.
root@ns1:~#

I replaced my domian name othe than that it is unedited

 

When using ISPConfig, do not modify any files in /etc/bind.
When using the ISPConfig autoinstall, check the preconditions in chapters 1 and 2 of https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/ . IP-address of server is entered in the /etc/hosts file.

 

I have learnt that the hard way years ago about the editing files

and well going back through step 1 and 2 changed nothing
but I did notice that bind9.service did not start at all
and neither did named

now I would expect that they should after a reboot but I started them and tested after starting each both need to be running for the DNS server to respond to requests

 

Indeed they should. You should find what prevents them starting. I would assume systemd starts them but they fail for some reason. Or did you check they really are not started at all? That would also be an error.