Open mdavids opened 6 years ago
From a client-perspective: resolving using ipv6 does not seem to work. As in: $ dig -6 example.nl
produces a time-out only.
My /etc/resolv.conf was:
domain lan nameserver fe80::e695:6eff:fe40:298c nameserver 192.168.8.1
And indeed, the fe80::e695:6eff:fe40:298c does nothing.
However, I am now running 1.5-beta-201803011326 and my /etc/resolv.conf is:
domain lan nameserver 192.168.8.1 nameserver fd48:430c:f4bc::1
and 'dig -6 example.nl' works:
;; SERVER: fd48:430c:f4bc::1#53(fd48:430c:f4bc::1)
Can be closed?
There is one more thing we need to test, I seem to recall the ULA address fd48:430c:f4bc::1 to not be set by openwrt if there is no IPv6 on the routers public side. Which, if so, causes a big problem, because then Unbound won't start (you can configure either hard IP addresses or 'everything' but not 'everything on iface x', AFAIK).
SPIN/Valibox announces itself as IPv4-local resolver (192.168.8.1) via DHCP. But how does this work for IPv6? I noticed a fe80::e695:6eff:fe40:298c in /etc/resolv.conf at some point. Does this work, is this right?
I guess this requires some further testing.