Please try if
pihole checkout ftl fix/pihole_ptr
resolves the issue for you.
This is actually a tricky situation. What we did before v5.9 was replying with
pi.hole only for the address defined in
setupVars.conf (which may have been wrong).
The new behavior is to reply with
pi.hole for every address for which a local interface exists which runs inline with our new behavior to reply with the address of the most suitable interface when querying
pi.hole for a
This new behavior can be influenced by the users in a two ways:
- Config option
PIHOLE_PTR defaulting to
When you set this option to
false, Pi-hole will not add any PTR requests itself.
- Already existing
ptr-record entries in
/etc/dnsmasq.d/ take precedence over our automatic PTR replies.
Two things remain to be discussed:
Should we reply with
pi.hole as well or should there be an exception for these addresses ?
We provide PTR requests for other interfaces, too. This may be seen as a slight inconsistency, because
PTR 192.168.4.1 may give you
A pi.hole would never give you
192.168.4.1 if this is not the interface you are connected to.