Unbound package updated to 1.4.13

wagonza

check your PM

wagonza

Ok package updated to handle @serialdie's problem. Updated to 1.4.13_01

serialdie

wagonza,

Thank you for the update.

Please bare with me as my pkg refresh is very slow as I mention before.

Thanks!

Edit:

Updating now. :)

wagonza

All ok?

serialdie

@wagonza:

All ok?

wagonza,

Its all perfect!!! :D

Its even faster now!
no more waiting for my pkg repo to load :D

Thank You!

Pay pal Donations?

wagonza

Good to hear!

Donations would be great! -> http://pfsense.org/donate.html and if you do donate, just mention its for Unbound.
Thanks!

serialdie

@wagonza:

Good to hear!

Donations would be great! -> http://pfsense.org/donate.html and if you do donate, just mention its for Unbound.
Thanks!

Awesome will do that. :)

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.

wagonza

@serialdie:

Awesome will do that. :)

thanks.

@serialdie:

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>