pfSense keeps sending AAAA record requests to local resolver when using "ignore local DNS"
-
I'm observing a strange issue.
I have been playing with pfBlockerNG Unbound python "DNS Reply Logging" to see what clients are requesting.
However: pfSense itself (127.0.0.1) is such a MASSIVE requestor that it's flooding the DNS Reply log.
Since my pfSense has no need (resolution wise) to use the built-in resolver, I thought I'd configure pfSense not to use it.
This is done in SYSTEM -> GENERAL SETUP - DNS RESOLUTION BEHAVIOUR by setting up WAN override (i use DHCP) and choose "use remote DNS, ignore local DNS".This removed pfSense from the reply logging when it comes to A records.
But my reply logging i is still spammed massively by AAAA record requests from 127.0.0.1 - mostly returning SOA records, but also for AAAA records on SOA servers.My pfSense/network is not using IPv6, an pfSense is set to NONE in IPv6 address fields on all interfaces. I understand that should have no influence on asking for AAAA records over IPv4,
but why is my pfSense flooding my resolver with AAAA requests when it's not even supposed to use the local DNS server?Ex. from DNS reply Log:
DNS-reply,Dec 10 18:15:53,resolver,AAAA,SOA,180,la1.akamaiedge.net,127.0.0.1,SOA,unk
DNS-reply,Dec 10 18:15:53,resolver,AAAA,SOA,180,a1-192.akamaiedge.net,127.0.0.1,SOA,unk
DNS-reply,Dec 10 18:15:53,resolver,AAAA,SOA,180,la3.akamaiedge.net,127.0.0.1,SOA,unk
DNS-reply,Dec 10 18:15:53,resolver,AAAA,SOA,180,n4dsce9.akamaiedge.net,127.0.0.1,SOA,unk
DNS-reply,Dec 10 18:15:53,resolver,AAAA,SOA,180,n2dsce9.akamaiedge.net,127.0.0.1,SOA,unk:
