[Support] Bind9

[VRx]

@rwysocki_bones

If You cleared config it is possible until there is no named.conf file.
You could try to start container, and then log in Web UI, there should be information about the need to create a configuration.
After this, supervisor should start without errors.

[rwysocki_bones]

On 5/31/2022 at 5:21 PM, VRx said:

@rwysocki_bones

If You cleared config it is possible until there is no named.conf file.
You could try to start container, and then log in Web UI, there should be information about the need to create a configuration.
After this, supervisor should start without errors.

I've completely re-installed the docker container, fresh install.
It didn't help, restarting the server seemed to work, but it went down again (I think next time docker container was restarted)
I have 2 Unraid servers so I even tried to copy the known working config from the other server, but still failing. tried installing it as host'ed network and as br0 with static IP, didn't work either way.
only things I can think off is that the working server is running combination of older version unraid and this docker container.

server1:

UNRAID 6.9.2 with [pwa666/[email protected]:b76ee59003e8eb4cd5199f72c87f5c89903fabb9992d30d93126c0f6687fee9a]

 

server2:

URAID 6.10.1 with [pwa666/[email protected]:6e315ba61f7d29b2d1cdf0012109753c461666db1fceba687ff3fb209231d8b9] (one version behind)

Also I am scared to update server2 to current 6.10.2 as there's an warning message "WARNING: combination of NIC using tg3 driver and Intel VT-d enabled may cause DATA CORRUPTION on some platforms."

I am running PowerEdge R730 8xLFF currently running the internal Ethernet card, but will be adding an Mellanox MCX311A-XCAT

 

EDIT----
I've also found that server1 has 2 files inside appdata that the server2 does not:
managed-keys.bind
managed-keys.bind.jnl

Edited June 3, 2022 by rwysocki_bones
added info about the managed-keys

[VRx]

@rwysocki_bones
go to docker console and execute:
/usr/sbin/named -4 -c /etc/bind/named.conf -L /var/log/named.log
Wait about 1 minute, check if named is not running using ps aux command, and then paste here /var/log/named.log content.
 

10 hours ago, rwysocki_bones said:

I've also found that server1 has 2 files inside appdata that the server2 does not:
managed-keys.bind
managed-keys.bind.jnl

This files are created automatically when You initiate first configuration from WebUI (watch attached screen)

If You cleared all config, first of all, run bind container, go to webUI, Create Primary Configuration File, and then check if proces 'named' is running.
If it is running, send me PM, I try to help You to copy configuration or maybe configure one from them as master, and second as slave DNS (in this case you will have to edit zones configuration only on the master)

 

!!! You can't copy only particular config files, but some others not !!!
 

[rwysocki_bones]

Progress! running your command gave me this in the log file, so it must be permissions issue, I am unsure what's wrong tho, I've noticed some of my appdata folders are root:root and some are nobody:users.

06-Jun-2022 01:04:36.847 general: error: directory '/etc/bind' is not writable
06-Jun-2022 01:04:36.847 config: error: /etc/bind/named.conf:6: parsing failed: permission denied
06-Jun-2022 01:04:36.848 general: critical: loading configuration: permission denied

# ls /mnt/user/appdata -l

drwxr-xr-x 1 nobody users  42 Jun  3 02:43 bind9/
# ls /mnt/user/appdata/bind9/ -l
-rw-r--r-- 1 nobody users 170 Jun  3 02:43 local.hosts
-rw-r--r-- 1 nobody users 513 Jun  3 02:38 named.conf

 

[VRx]

@rwysocki_bones paste ownership and privileges from Container Console:
 

ls -la /etc/bind

 

Did You create new config by WebUI like I asked in previous post?

[rwysocki_bones]

59 minutes ago, VRx said:

@rwysocki_bones paste ownership and privileges from Container Console:
 

ls -la /etc/bind

 

Did You create new config by WebUI like I asked in previous post?

# ls -la /etc/bind
drwxr-xr-x    1 99       users           42 Jun  3 02:43 .
drwxr-xr-x    1 root     root           746 Jun  6 01:02 ..
-rw-r--r--    1 99       users          170 Jun  3 02:43 local.hosts
-rw-r--r--    1 99       users          513 Jun  3 02:38 named.conf

Yes I have, I've fully reinstalled the application and removed the bind9 folder from appdata then installed the container from CA and then go to GUI and set it up

[VRx]

@rwysocki_bones

chown root:root /etc/bind/*
chmod 664 /etc/bind/*

And then try to run named using container console:
 

/usr/sbin/named -4 -c /etc/bind/named.conf -L /var/log/named.log

And then check /var/log/named.log

[rwysocki_bones]

7 minutes ago, VRx said:

@rwysocki_bones

chown root:root /etc/bind/*
chmod 664 /etc/bind/*

And then try to run named using container console:
 

/usr/sbin/named -4 -c /etc/bind/named.conf -L /var/log/named.log

And then check /var/log/named.log

I've run the chown and chmod on the docker container, output from named:
 

06-Jun-2022 07:47:50.274 general: info: loading configuration from '/etc/bind/named.conf'
06-Jun-2022 07:47:50.275 general: error: directory '/etc/bind' is not writable
06-Jun-2022 07:47:50.275 config: error: /etc/bind/named.conf:6: parsing failed: permission denied
06-Jun-2022 07:47:50.276 general: critical: loading configuration: permission denied
06-Jun-2022 07:47:50.276 general: critical: exiting (due to fatal error)

and ls -la after:
 

#ls -la /etc/bind
total 8
drwxr-xr-x    1 99       users           42 Jun  3 02:43 .
drwxr-xr-x    1 root     root           746 Jun  6 01:02 ..
-rw-rw-r--    1 root     root           170 Jun  3 02:43 local.hosts
-rw-rw-r--    1 root     root           513 Jun  3 02:38 named.conf

and from the UNRAID cli:
 

# ls /mnt/user/appdata/bind9/ -la
total 8
drwxr-xr-x 1 nobody users  42 Jun  3 02:43 ./
drwxrwxrwx 1 nobody users 230 Jun  6 05:02 ../
-rw-rw-r-- 1 root   root  170 Jun  3 02:43 local.hosts
-rw-rw-r-- 1 root   root  513 Jun  3 02:38 named.conf

should i chown the bind9 folder as root:root?

[VRx]

1 hour ago, rwysocki_bones said:

should i chown the bind9 folder as root:root?

Try to set (777) rwx for all on bind9 folder

[rwysocki_bones]

14 hours ago, VRx said:

Try to set (777) rwx for all on bind9 folder

It came online! i've set the files to 664 but folder to 777 and it works now.\

 

Thanks

[VRx]

I tried to do few tests on unraid version 6.10 but there are so many bugs on various applications with this version that I went back to version 6.9.2.
Some problematic applications are necessary for me for everyday use of the server. In this situation I would have to spend a lot of time diagnosing problems and correcting them, but this is not my responsibility, apparently other developers are not interested in their applications.
There could be some issue with file priviliges (for example rndc key), but correcting it manually should help.

[VRx]

New version pushed!
* fixed bugs with UnraidOS >6.9.2

 

@rwysocki_bones thanks for the report and your time

[VRx]

Healthcheck has been added for new users who do a fresh install.

Sometimes I got signals about errors in the docker log telling that bind is not running, such a situation can take place and it is not a bad thing. After creating initial configuration using the GUI, there will stop logging this info.

For this purpose, a healthcheck has been added, which will signal when the docker status is healthy or not.
If it shows that it is healthy, you don't have to worry about errors in docker logs.

[eagle470]

I'm looking at standing this up, but I'm wondering it if I can have two instances running as a cluster? Or in sync type scenario?

[VRx]

@eagle470 You can run one as master, and second as slave dns. Master after zone modification can send query to slaves, then slaves know that they must get update from master.

[tuxbass]

I'm running an old bind version from sameersbn/bind image that was last updated 3y ago:
 

BIND 9.16.1-Ubuntu (Stable Release) <id:d497c32>
webmin ver: 1.941

Is there a straight-forward enough way to upgrade to your image instead?
Note current bind installation configuration/appdata bound to /data in the container looks like:
 

┌─[server]─[/mnt/user/appdata/bind]
└──╼ + tree -L 3
.
|-- bind
|   |-- etc
|   |   |-- bind.keys
|   |   |-- db.0
|   |   |-- db.127
|   |   |-- db.255
|   |   |-- db.empty
|   |   |-- db.local
|   |   |-- db.root
|   |   |-- named.conf
|   |   |-- named.conf.default-zones
|   |   |-- named.conf.local
|   |   |-- named.conf.local~
|   |   |-- named.conf.options
|   |   |-- rndc.key
|   |   `-- zones.rfc1918
|   `-- lib
|       |-- mydomain.eu.hosts
|       `-- mydomain2.eu.hosts
`-- webmin
    `-- etc
        |-- acl
        |-- adsl-client
        |-- ajaxterm
        |-- apache
        |-- at
        |-- ...etc

 

Second, 2 years ago (near beginning of this thread) it was stated '- changed network mode to bridge as default' -- now it still defaults back to host network. Does it mean we should be running it in host network again?

Edited Monday at 09:14 PM by tuxbass