Multiplexing Null blocking [implemented]


#1

When using Null blocking, the content of gravity.list is pushed into DNSmasq to form the table. This is done once for IPv4 and then for IPv6 and so doubling the size of the table.

Why not only push IPv4 into the table and omit IPv6. Would this save memory and if so then on a hit, the blocking result is doubled only then to a IPv4 and a IPv6 null address returned to the client.

Remebering writing earlier about this and then I think the problem was that Pi-hole could not manipulate the reply by DNSmasq. If manuplilation is possible now, then you could think of putting a nxdomain in and translate that to what user choose to be returned, blocking page, Null or nxdomain.


#2

No, one record is used for both, IPv4 and IPv6. This is a change that is not released yet (it is in development). It will be released with Pi-hole v4.2.


#3

Great that is coming in version 4.2 and I can already see now in development. I did not check it first by comparing logs between 4.1 and development.


#4

Has this been implemented yet?

Assuming this is referencing the address=/example.com/# syntax.

I’m currently on DEV.


#5

I was writing about combining IPv4 and IPv6 for gravity.list so that the memory usage for that list is reduced to 50%. This was already tackled by DL6ER just before.

The DNSmasq dedicated wildcard file is also working in DEV release/v4.2