IPv6 seems to break unbound 23.09.1

Martin_D

Setting up ipv6 stops unbound from starting up I can’t figure it out

My setup is

IPv6 Configuration Type DHCP6

Request only an IPv6 prefix Yes

DHCPv6 Prefix Delegation size 56

Send IPv6 prefix hint Yes

Jan 18 10:07:02 unbound 94775 [94775:0] error: Bad local-data RR pfSense.home. AAAA fe80::2694:cbff:fedd:4bd1%igc0 Jan 18 10:07:02 unbound 94775 [94775:0] fatal error: Could not set up local zones Jan 18 10:08:02 unbound 95771 [95771:0] error: error parsing local-data at 19 'pfSense.home. AAAA fe80::2694:cbff:fedd:4bd1%igc0': Conversion error, ip6 addr expected Jan 18 10:08:02 unbound 95771 [95771:0] error: Bad local-data RR pfSense.home. AAAA fe80::2694:cbff:fedd:4bd1%igc0

Gertjan

@Martin_D said in IPv6 seems to break unbound 23.09.1:

Bad local-data RR pfSense.home. AAAA fe

"pfSense" is ok for me, as I use the same host name

But the domain "home dot' can't be ok : why not a "home dot arpa" = "home.arpa" ?
You must use a syntax valid domain name ....

Test :

[23.09.1-RELEASE][root@pfSense.bhf.net]/root: dig pfsense.bhf.net AAAA +short
2a01:cb19:dead:beef:92ec:77ff:fe29:392c
[23.09.1-RELEASE][root@pfSense.bhf.net]/root: dig -x 2a01:cb19:dead:beef:92ec:77ff:fe29:392c +short
pfSense.bhf.net.

@Martin_D said in IPv6 seems to break unbound 23.09.1:

IPv6 Configuration Type DHCP6

Request only an IPv6 prefix Yes

DHCPv6 Prefix Delegation size 56

Send IPv6 prefix hint Yes

These are the DHCPv6 settings.
Every ISP needs these according their own criteria.

Mine needs close to nothing :

as 'they' (actually the DHCP6 server in my ISP box) gives me just one /64 .....
I guess IPv6 (DHCPv6) will be straight forward somewhere in the future. After all, DHCP(v4) took also a decade or so to settle in and become 'simple'.

My 'unbound' uses :

Probably not the most perfect setting, but "its work for me", unbound is happy and resolves over IPv6 just fine.

Btw : I'm using 23.09.1 also.

Martin_D

@Gertjan

Thanks changed the name but still getting this error

Gertjan

@Martin_D

can you check what unbound uses when it starts :

edit : also : restart unbound : go to the Services > DNS Resolver > General Settings page, without modifying anything, Hit Save and then Apply.

Martin_D

@Gertjan

local-zone: "home.arpa." transparent

local-data-ptr: "127.0.0.1 localhost.home.arpa"

local-data: "localhost. A 127.0.0.1"

local-data: "localhost.home.arpa. A 127.0.0.1"

local-data-ptr: "::1 localhost.home.arpa"

local-data: "localhost. AAAA ::1"

local-data: "localhost.home.arpa. AAAA ::1"

local-data-ptr: "Removed pfSense.home.arpa"

local-data: "pfSense.home.arpa. A Removed"

local-data-ptr: "fe80::2694:cbff:fedd:4bd1%igc0 pfSense.home.arpa"

local-data: "pfSense.home.arpa. AAAA fe80::2694:cbff:fedd:4bd1%igc0"

Gertjan

@Martin_D said in IPv6 seems to break unbound 23.09.1:

local-data: "pfSense.home.arpa. AAAA fe80::2694:cbff:fedd:4bd1%igc0"

That's the one I do not have :

local-data: "pfSense.brit-hotel-fumel.net. AAAA 2a01:cb19:dead:beef:92ec:77ff:fe29:392c"

I've no "%igc0" (the network name part) and for ùme, unbound has troubles this "%igc0".
I've no "fe80" IPv6, but a 'real' "2a01:xxx" as that's part of the prefix DHCPv6 client on WAN obtained.
For me, 2a01:cb19:dead:beef:92ec:77ff:fe29:392c was assigned as the LAN IPv6.

The error :

Conversion error, ip6 addr expected

makes me thing that unbound doesn't understand the "%igc0" part.

Probably not related, but this one

Request only an IPv6 prefix Yes

The prefix or prefixxes (multiple /64) are for your LAN(s).
You don't want an Ipv6 for your pfSense WAN ? I tend to not check that option.

Another one : what do you have here :