Project

General

Profile

Actions

Bug #9567

closed

Unbound DNS Resolver does not start up when using IPv6 DHHCPv6 WAN DHCPv6 LAN coupled with v6 Prefix Delegation

Added by Eric Veum almost 5 years ago. Updated over 3 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
05/29/2019
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
All

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.

Actions

Also available in: Atom PDF