Unbound DNS fails to start after upgrade to 21.1.6

[ika]

Hi,

after upgrade Opnsense from 21.1.5 to 21.1.6 Unbound DNS service fails to start. Local resolving is slow and there are error messages as following:

Code: [Select]

2021-06-02T12:30:32 unbound[48476] [48476:0] fatal error: Could not set up local zones
2021-06-02T12:30:32 unbound[48476] [48476:0] error: Bad local-data RR selm01.lab.domain.cc device.local IN A 192.168.n.n
2021-06-02T12:30:32 unbound[48476] [48476:0] error: error parsing local-data at 34 'selm01.lab.domain.cc device.local IN A 192.168.n.n': Syntax error, could not parse the RR's type
Everything was working fine prior upgrade. Any ideas?

[franco]

Maybe https://github.com/opnsense/core/commit/64268c571

Can you try to revert and restart unbound?

# opnsense-patch 64268c571

Curious what the issue is supposed to be since we only refactored data acquire for the configuration write..


Cheers,
Franco

[ika]

Hi Franco,

I did # opnsense-patch 64268c571 and restarted unbound. Unbound is able to start correctly again.

cheers,
IKA

[franco]

Not so fast... can you send me a diff of /var/unbound/host_entries.conf when it works and when it doesn't? (apply patch again to revert).

PM or mail is fine (franco@opnsense.org)


Thanks,
Franco

[ika]

Hi,

Done. Sent as PM.

IKA

[franco]

Hi IKA,

Thanks, can you try this patch instead? https://github.com/opnsense/core/commit/7ef730ac1c

# opnsense-revert opnsense
# opnsense-patch 7ef730ac1c


Cheers,
Franco

[ika]

Hi Franco,

Thanks, can you try this patch instead? https://github.com/opnsense/core/commit/7ef730ac1c

# opnsense-revert opnsense
# opnsense-patch 7ef730ac1c

I can confirm that unbound is working after patch 7ef730ac1c application and restart of unbound. Performed diff between original correct host_entries.conf and host_entries.conf after this patch. No difference.

Cheers,
IKA

[franco]

Thanks, this patch will be part of 21.1.7.


Cheers,
Franco

[sesquipedality]

Can confirm that this fix worked for me.  I had to log in via IP and disable unbound prior to applying though, since DNS was not resolving while unbound was enabled.  Once the patch was applied, I could restart unbound.

Thanks for fixing this.