Unbound package updated to 1.4.13

wagonza

Awesome will do that. :)

thanks.

I have one question. have you try after the upgrade to add a static entry under dhcp? I just did that and it cause unbound to massively crash… It wouldnt come back up from the webui I had to call it from cli.
I wanted to see if any body can replicate my issue.

hrmm odd. Since when adding a static DHCP entry it doesn't update Unbound. Unbound only gets updated when it is re-saved - as, currently, there is no way Unbound knows that the static DHCP mappings have been updated. I'll see if I can replicate what you see in the morning.

serialdie

wagonza,

Well they have to work together some how since I have Register DHCP static mappings set to on.
Thanks for the help and awesome work.

wagonza

Yeah they do work together, but the list doesn't get updated in Unbound until you re-save on Unbound. Unlike the current DNS Forwarder which has a background process updating it automatically when leases get updated.

Unbound, currently, has no way of knowing when that list is updated so it wont auto-update.

serialdie

@wagonza:

Yeah they do work together, but the list doesn't get updated in Unbound until you re-save on Unbound. Unlike the current DNS Forwarder which has a background process updating it automatically when leases get updated.

Unbound, currently, has no way of knowing when that list is updated so it wont auto-update.

ah! That make since.

:)

GLR

Hello,
I am afraid but on my side : I have an issue : I am not able to get the ACLs (unbound_acls.php) and status (unbound_status.php) pages.
I am redirected back to the standard settings page (pkg_edit.php?xml=unbound.xml&id=0)
So it seems there is a problem with the xml config (?)

wagonza

@GLR:

Hello,
I am afraid but on my side : I have an issue : I am not able to get the ACLs (unbound_acls.php) and status (unbound_status.php) pages.
I am redirected back to the standard settings page (pkg_edit.php?xml=unbound.xml&id=0)
So it seems there is a problem with the xml config (?)

That generally means Unbound is not running as it checks to see if the process is running and if not it redirects you to that first setup page.
You might have config errors which I would be interested in seeing. So from a shell you can run unbound-checkconf - it should return no errors.

GLR

Yes, now that Unbound is running, the tab are correctly displayed. So it is not so serious…
But anyway, it is not a normal behaviour : How can we set the ACLs before starting it in that case ?

wagonza

@GLR:

Yes, now that Unbound is running, the tab are correctly displayed. So it is not so serious…
But anyway, it is not a normal behaviour : How can we set the ACLs before starting it in that case ?

ok good to hear. You raise a good point though i'll remove that check for the ACL's tab.

GLR

It would be great, thanks !

wagonza

Package updated to 1.4.13_02 and ACLs can now be edited before starting Unbound.

GLR

Confirmed OK for me. Thanks again for the prompt fix !

Btw, I would have some features requests for Unbound.
I am still doing some tunning by hand in the config file…
Is there such a list available somewhere ?

wagonza

Nope, no list, but you can PM them when you have the list.

GLR

I think there is still something that remains not exact in the settings tab :

Network interface
The network interface(s) the Unbound DNS server will query from.

This is wrong, this option defines the Unbound config attribute "interface:", so the interface on which Unbound will bind/listen.
And indeed, it generates this entry in the config file :

Interface IP(s) to bind to

interface: <ip>> interface:

This interface is listened to for queries from clients, and answers to clients are given from it.

Whereas Unbound config attribute "outgoing-interface:" is not available in the settings pages.

outgoing-interface:
This interface is used to send queries to authoritative servers and receive their replies.

And actually I also need this option to direct some queries to an authoritative NS through an IPSec tunnel. :-</ip>

Tikimotel

Only just updated to 1.4.13_02 but get get this error:


php: /pkg_mgr_install.php: The command '/usr/local/sbin/unbound-control start' returned exit code '1', the output was '[1317586911] unbound[7976:0] error: setsockopt(..., SO_RCVBUF, ...) failed: No buffer space available [1317586911] unbound[7976:0] fatal error: could not open ports'

Was I too quick or is it broken?

serialdie

[code][quote]
Yeah they do work together, but the list doesn't get updated in Unbound until you re-save on Unbound. Unlike the current DNS Forwarder which has a background process updating it automatically when leases get updated. 

Unbound, *currently*, has no way of knowing when that list is updated so it wont auto-update.
[/quote]

Wagonza,

The same issue happen. I can replicate this in two pfsense systems. every time I make a static entry or change the hostname of the static entry unbound crashes.
:

[code]
Oct 2 18:36:32	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Oct 2 18:36:32	dhcpd: All rights reserved.
Oct 2 18:36:32	dhcpd: Copyright 2004-2011 Internet Systems Consortium.
Oct 2 18:36:32	dhcpd: Internet Systems Consortium DHCP Server 4.2.1-P1[/code]

unbound.log:

[code]
Oct  2 18:36:31 craken unbound: [19729:0] info: service stopped (unbound 1.4.13). [/code][/code]

wagonza

@Tikimotel:

Only just updated to 1.4.13_02 but get get this error:


php: /pkg_mgr_install.php: The command '/usr/local/sbin/unbound-control start' returned exit code '1', the output was '[1317586911] unbound[7976:0] error: setsockopt(..., SO_RCVBUF, ...) failed: No buffer space available [1317586911] unbound[7976:0] fatal error: could not open ports'

Was I too quick or is it broken?

Nope looks like something else is wrong on your system. Network card ok?

wagonza

@serialdie:

[code][quote]
Yeah they do work together, but the list doesn't get updated in Unbound until you re-save on Unbound. Unlike the current DNS Forwarder which has a background process updating it automatically when leases get updated. 

Unbound, *currently*, has no way of knowing when that list is updated so it wont auto-update.
[/quote]

Wagonza,

The same issue happen. I can replicate this in two pfsense systems. every time I make a static entry or change the hostname of the static entry unbound crashes.
:

[code]
Oct 2 18:36:32	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Oct 2 18:36:32	dhcpd: All rights reserved.
Oct 2 18:36:32	dhcpd: Copyright 2004-2011 Internet Systems Consortium.
Oct 2 18:36:32	dhcpd: Internet Systems Consortium DHCP Server 4.2.1-P1[/code]

unbound.log:

[code]
Oct  2 18:36:31 craken unbound: [19729:0] info: service stopped (unbound 1.4.13). [/code]

ahh - this is a side affect of having to deal with the DHCP Leases bug problem. I'm about to leave for Washington and then back to SA. So will only be able to get to this towards the end of the week.[/code]

wagonza

@GLR:

I think there is still something that remains not exact in the settings tab :

Network interface
The network interface(s) the Unbound DNS server will query from.

This is wrong, this option defines the Unbound config attribute "interface:", so the interface on which Unbound will bind/listen.
And indeed, it generates this entry in the config file :

Interface IP(s) to bind to

interface: <ip>> interface:

This interface is listened to for queries from clients, and answers to clients are given from it.

Whereas Unbound config attribute "outgoing-interface:" is not available in the settings pages.

outgoing-interface:
This interface is used to send queries to authoritative servers and receive their replies.

And actually I also need this option to direct some queries to an authoritative NS through an IPSec tunnel. :-</ip>

Yeah you are correct - i'll update the wording etc and push out a new update. Most likely only towards the end of the week as Im off back home now.
I got your PM btw so will look into those features.

Tikimotel

@wagonza:

@Tikimotel:
Only just updated to 1.4.13_02 but get get this error:
php: /pkg_mgr_install.php: The command '/usr/local/sbin/unbound-control start' returned exit code '1', the output was '[1317586911] unbound[7976:0] error: setsockopt(..., SO_RCVBUF, ...) failed: No buffer space available [1317586911] unbound[7976:0] fatal error: could not open ports'
Was I too quick or is it broken?
Nope looks like something else is wrong on your system. Network card ok?

Thnx I Fixed it!
Changed "kern.ipc.maxsockbuf" back to "default" in system tunables.
Funny, I changed it whilst running the previous unbound 1.4.13_01 update and it was and stayed OK.

serialdie

@wagonza:

@serialdie:

[code][quote]
Yeah they do work together, but the list doesn't get updated in Unbound until you re-save on Unbound. Unlike the current DNS Forwarder which has a background process updating it automatically when leases get updated. 

Unbound, *currently*, has no way of knowing when that list is updated so it wont auto-update.
[/quote]

Wagonza,

The same issue happen. I can replicate this in two pfsense systems. every time I make a static entry or change the hostname of the static entry unbound crashes.
:

[code]
Oct 2 18:36:32	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Oct 2 18:36:32	dhcpd: All rights reserved.
Oct 2 18:36:32	dhcpd: Copyright 2004-2011 Internet Systems Consortium.
Oct 2 18:36:32	dhcpd: Internet Systems Consortium DHCP Server 4.2.1-P1[/code]

unbound.log:

[code]
Oct  2 18:36:31 craken unbound: [19729:0] info: service stopped (unbound 1.4.13). [/code]

ahh - this is a side affect of having to deal with the DHCP Leases bug problem. I'm about to leave for Washington and then back to SA. So will only be able to get to this towards the end of the week.[/code]

Wagonza,

No rush I am just reporting :) I am not in a hurry since I dont change hostnames very often. I do create a lot of static entrys but I work around it by adding a cron job.
Thank you for your fast response.