Re: filter-aaaa-on-v4 does not filter AAAA if there is no existing A Record with the same FQDN - working as designed?

So we can assume that this is working as designed?! However, it would be very interesting to know why this policy does not filter Records when there is no A record. From my point of view this policy is useless. If we want to prevent clients from receiving any Records for every case, th

filter-aaaa-on-v4 does not filter AAAA if there is no existing A Record with the same FQDN - working as designed?

Hi all, I am not sure if the following behavior is working as designed or not. I have configured filter--on-v4 to yes on my DNS Server. Regarding this filter option, I have a working and a non working example: Working example ( was filtered): # dig www.google.com. +noall +answer +