Project

General

Profile

Bug #9654

After reboot, the DNS resolver must be restarted before it will advertise the ipv6 DNS address of the router.

Added by Rick Coats about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
07/28/2019
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.4.4-p3
Affected Architecture:

Description

When pfsense ipv6 is configured with DHCPv6 disabled and RA in "Unmanaged" mode, then after reboot, until the resolver is restarted the DNS does not know that the router has an ipv6 address.

In my configuration I have the DCHP Registration unchecked in the resolver, so I do not have unbound getting restarted due to DHCP events.

After reboot, with a working ipv6 setup, if you go to Diagnostics/DNS lookup and lookup pfsense.mydomain.com, it will only reply with ipv4 address of router.

Examining /var/unbound/host_entries.conf I see that the local-data: lines for the ipv6 for router are missing.

Looking at /var/etc/radvd.conf is missing a lot of information as if it hasn't been configured yet.

Packet capture of RA packets show that indeed, the DNS is not being advertised.

Manually restarting unbound service fixes all of this and it is good until next reboot.

Posted at:
https://forum.netgate.com/topic/145162/after-reboot-the-dns-resolver-must-be-restarted-before-it-will-advertise-the-ipv6-address-of-the-resolver

I am running 2.4.4-RELEASE-p3 (amd64)
Installed Packages (latest version):
acme
Avahi
nut
openvpn-client-export

History

#1 Updated by Jim Pingle about 1 month ago

  • Category set to DNS Resolver
  • Priority changed from High to Normal

Also available in: Atom PDF