You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded my Pi-Hole installation from 5.25.2 to the 6.0.2 release and I noticed a new behavior in how new IPv6 clients are resolved to their hostnames with PTR queries.
I saw below change in the code base between 5.x and 6.x. It adds a delay in resolving new IPv6 clients.
The caveat is, that, as long as resolver.refreshNames is not set to ALL, that client hostname is never going to be resolved, except, if there is another new client (after the delay time). In that case, the previous client hostname is resolved.
Is this the expected behavior? I would have expected, that at least after the delay, that new IPv6 client should be resolved even though resolver.refreshNames is set to the default value of IPV4_ONLY. What is the wanted behavior here?
The text was updated successfully, but these errors were encountered:
Hi,
I upgraded my Pi-Hole installation from 5.25.2 to the 6.0.2 release and I noticed a new behavior in how new IPv6 clients are resolved to their hostnames with PTR queries.
I saw below change in the code base between 5.x and 6.x. It adds a delay in resolving new IPv6 clients.
FTL/src/resolve.c
Lines 946 to 958 in ac500d5
The caveat is, that, as long as resolver.refreshNames is not set to ALL, that client hostname is never going to be resolved, except, if there is another new client (after the delay time). In that case, the previous client hostname is resolved.
Is this the expected behavior? I would have expected, that at least after the delay, that new IPv6 client should be resolved even though resolver.refreshNames is set to the default value of IPV4_ONLY. What is the wanted behavior here?
The text was updated successfully, but these errors were encountered: