DNS forwarding broken in 162?

Networking DNS
1

Hi there,
I noticed that forwarding foreign DNS-zones stopped working after updating to core 162 here. Is this a known problem? If so, is there a work-around yet?
TIA!

Edit: Disabling DNSSEC seems to solve the problem, so rather DNSSEC-query/handling seem to have changed. Formerly it worked also when it was enabled?

2

Not to my knowledge. I haven’t seen any communication on the dev mailing list on this and there is nothing in the IPFire bugzilla.
I don’t use this option on my production IPFire or on my vm testbed systems so have no personal experience of what you have found.

unbound was updated from 1.13.1 to 1.13.2 in Core Update 162 and its changelog info mentions dnssec a few times but I don’t have enough knowledge to tell if this might have caused the problem or not.

Probably worth raising as a bug in the IPFire bugzilla and providing your log info of the problem.

https://wiki.ipfire.org/devel/bugzilla
https://bugzilla.ipfire.org/

Your IPFire people email address and password will act as login credentials.

3

Hi Adolf,
thanks, I filed a new bug: 12766 – Core 162: DNS forwarding broken with DNSSEC enabled

2 Likes