[Support] Bind9


Recommended Posts

  • 2 weeks later...

- Some improvements  in webmin bind module.
RNDC is working now from WebUI. So easy zone update is possible thru webui, without restarting bind or whole container.
Just click on "Apply Zone" in top right corner when zone edited.

- changed network mode to bridge as default

- default webui password updated ( dificult -> difficult )


*Image is lightweight because build from alpine linux, most popularn bind+webmin on docker hub are based on ubuntu (4-5 times heavier).

Link to comment
On 7/30/2021 at 6:22 AM, VRx said:

@Owner did You have any error message?
If You have error like attached below, this is not image problem. But known problem that sometimes pointing to /mnt/user is crashing.
Let me know if message is different maybe.

error.PNG

Yes this it is. Seems tho that the system keeps the port binded after removal.

Link to comment
Just now, Owner said:

Yes this it is. Seems tho that the system keeps the port binded after removal.

Can I use /mnt/disk/appdata/bind9 instead. As far I know the reason for error was the port 53 had to be changed to 5353 but upon removal it doesn't removal the bind of port. I will look into this more. On how to remove the bind port 5353 error.

Link to comment
5 hours ago, Owner said:

Can I use /mnt/disk/appdata/bind9 instead.

Yes You can. This change should resolve this problem.
 

5 hours ago, Owner said:

As far I know the reason for error was the port 53 had to be changed to 5353 but upon removal it doesn't removal the bind of port.

You cannot change port to 5353, because DNS Service is using port 53, and all operating systems are using this port to resolve hostnames by default.
Maybe You have another service using this port, for example pihole container.

Can You please post some error message, and some logs from this container or maybe send me PM with this informations as You prefer?

There is a fix in progress, by the way of searching for solution, I found some other bugs.

Link to comment
On 8/1/2021 at 10:46 PM, VRx said:

Yes You can. This change should resolve this problem.
 

You cannot change port to 5353, because DNS Service is using port 53, and all operating systems are using this port to resolve hostnames by default.
Maybe You have another service using this port, for example pihole container.

Can You please post some error message, and some logs from this container or maybe send me PM with this informations as You prefer?

There is a fix in progress, by the way of searching for solution, I found some other bugs.

I will test it out port 5353 wasn't the issue. It was the starting up in general. Will give it a go and post some results

Link to comment
On 8/2/2021 at 2:17 PM, VRx said:

Update:
- Fixed env variables (setting admin password should now work properly)
- Fixed bind starting script (starting/restarting bind from webUI)

Reason behind 5353 is I use a dns server with OPNSense. No pi-hole. OPNSense has such blocking for better ease.

Link to comment
On 8/1/2021 at 10:46 PM, VRx said:

Yes You can. This change should resolve this problem.
 

You cannot change port to 5353, because DNS Service is using port 53, and all operating systems are using this port to resolve hostnames by default.
Maybe You have another service using this port, for example pihole container.

Can You please post some error message, and some logs from this container or maybe send me PM with this informations as You prefer?

There is a fix in progress, by the way of searching for solution, I found some other bugs.

I will try to figure out the unbinding issue. Not sure how that is caused. Still looking been away from forums

Link to comment
  • 2 weeks later...
  • 1 month later...
On 8/17/2021 at 4:36 AM, VRx said:

From now there will be weekly system update, every Sunday.
But every changes in application, as always, will be reported in this thread.

Awesome thanks. I will look at that but I don’t think I should need a custom bridge if my first dns sits on 192.168.75.1 and the other is on the Unraid box 192.168.75.3. But no doubt thanks for fixing those bugs. Much appreciated. 

Link to comment
  • 1 month later...
  • 2 weeks later...
2021-11-19 15:01:19,854 INFO supervisord started with pid 17
2021-11-19 15:01:20,857 INFO spawned: 'bind' with pid 39
2021-11-19 15:01:20,909 INFO exited: bind (exit status 1; not expected)
2021-11-19 15:01:21,912 INFO spawned: 'bind' with pid 73
2021-11-19 15:01:21,943 INFO exited: bind (exit status 1; not expected)
2021-11-19 15:01:23,946 INFO spawned: 'bind' with pid 107
2021-11-19 15:01:23,977 INFO exited: bind (exit status 1; not expected)
2021-11-19 15:01:26,981 INFO spawned: 'bind' with pid 141
2021-11-19 15:01:27,012 INFO exited: bind (exit status 1; not expected)
2021-11-19 15:01:28,013 INFO gave up: bind entered FATAL state, too many start retries too quickly

 

Is the default configuration needed (named.conf) before boot? 
Seems something is wrong with the entrypoint script/bin

Edited by Kanashii
Link to comment
  • 3 weeks later...
On 12/11/2021 at 9:34 PM, NeySlim said:

HI, how can I make bind to listen to ipv6 ?

I don't know how to remove de the -4 option, or add the -6 beside editing supervisor conf in container.

many thanks

 

Check for container update and update it.
Add new ENV:

IPV6=enable

Should work from now.

Link to comment
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.