Ubound spamming log and won't start after reboot

[A Former User]

Hi

Since I've activated IPv6 on my pfSense and updated to the latest community version (2.3.4-RELEASE-p1) my Ubound DNS Resolver doesn't start after reboot. I have to start it manually then it works.

At the same time the ubound does generate a lot of Log that says:

Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::1:1
Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::20c:29ff:fe88:1234
Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::20c:29ff:fe88:1234
Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::1:1
Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::1:1
Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::1:1
Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::1:1
Aug 28 08:58:29	unbound	57930:7	error: can't bind socket: Can't assign requested address for fe80::20c:29ff:fe88:1234

Don't have any idea why this happens… but maybe someone of you can give me a hint?

Edit: Okay.. already found some thing.. disabled ubound to bind to the ipv6 "Link-Local" interfaces... but why are they selected by default?