Project

General

Profile

Actions

Feature #14535

closed

DNS Unbound Resolver will still resolve IPv6 AAAA URLS when LAN and WAN are set to none for IPv6.

Added by Jonathan Lee almost 2 years ago. Updated almost 2 years ago.

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

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

Hello fellow redmine members,

I have noticed that the DNS unbound still resolves AAAA ipv6 when the LAN and WAN interface is set to NONE for ipv6, should the DNS unbound resolver auto disable AAAA when WAN is set to none for ipv6 as the LAN will never be able to resolve those?

This is what I have done to fix this issue as I have no IPv6 from ISP.

I still had to add the following into advanced config area of the unbound dns resolver

server:
do-ip4: yes
prefer-ip4: yes
do-ip6: no
prefer-ip6: no
private-address: ::/0
dns64-ignore-aaaa: *.

do-not-query-address: ::
do-not-query-address: ::1
do-not-query-address: ::/0*

Again all that is needed to fix this per John Poz is to add private-address: ::/0 and do-ip6: no prefer-ip6: no to the custom options.

pfSense when set to NONE for IPv6 does not adapt the DNS unbound resolver to also disable IPv6.

When this is left not changed in the DNS unbound the client side browsers all still attempt to access IPv6 URLS, leading to many errors on the client side end.

Can we also add a button to disable ipv6 inside of the unbound DNS resolver?

And or link the WAN to the DNS when it disables also disable AAAA?

My ISP does not provide IPv6 only IPv4.


Files

Actions

Also available in: Atom PDF