Bug #9567
closed
Unbound DNS Resolver does not start up when using IPv6 DHHCPv6 WAN DHCPv6 LAN coupled with v6 Prefix Delegation
0%
Description
When operating with a dual IPv4/IPv6 stack, on a consumer modem (Comcast),
with WAN DHCP single internet-routable IP /32 (NAT to RFC1918 as usual, static IPv4 LAN)
with WAN DHCPv6, and issued a /64 IPv6 block, and 'Track Interface' mode for the IPv6 LAN via tracking WAN),
and DHCPv6 services on LAN setup with Prefix Delegation in use.
the unbound DNS internal services fail to startup after a reboot -- and LAN DNS services are then not operational.
They have to be manually started from the UI console after reboot.
I suspect this is due to an order of operations for starting services in a BSD 'rc.conf'/init.d ordering or equivalent for pfsense, and
the fact that the FW has to send out the request for the /64.
If certain logs are needed for reproduction or debug, please advise.
Updated by Jim Pingle over 5 years ago
- Status changed from New to Not a Bug
I can't reproduce this here. I run a few VMs this way and the resolver starts as expected.
Please post on the Forum to discuss the problem more in-depth and gather more information.
Updated by Eric Veum almost 5 years ago
Jim -- Further analysis done, and studying interfaces changes during boot (those initially assigned), and later through DHCP6c, Full details in #9998
Updated by Marc Dorando about 4 years ago
Similar issue over here, 2.4.5-RELEASE-p1 having LAN, VLAN and WAN1, WAN2 (LoadBalancing&Failover) and IPv4, IPv6 and pfb_dnsbl (stable) and snort (stable). Unbound was starting before 2.4.5 without any issues.