Will Pi-hole start to use home.arpa. as the default value for dns.domain.name, instead of lan?
Could you explain the practical difference ?
$ xargs -n1 whois <<< 'lan. intranet. internal. private. corp. home. home.arpa.'
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
[..]
domain: HOME.ARPA
[..]
contact: technical
name: Internet Assigned Numbers Authority (IANA)
organisation: Internet Corporation for Assigned Names and Numbers (ICANN)
[..]
remarks: This domain is administered as part of the .ARPA zone
remarks: management, described at https://iana.org/domains/arpa
$ dig +short @8.8.8.8 home.arpa ns
blackhole-1.iana.org.
blackhole-2.iana.org.
$ dig +short @8.8.8.8 lan. ns
$
Its harder to hijack home.arpa.
Queries for the other domains dont get blackholed.
Adding to this:
.internal is explicitly reserved for private use by ICANN as of 29 July 2024, with the intended effect of reducing the usage of uncoordinated ad-hoc defaults (such as Pi-Hole’s current default `.lan`). This is also in the process of being standardised by the IETF.
Pi-Hole should certainly be adhering to ICANN/IETF recommendations, and use one of home.arpa or internal as the default DNS domain, not something like LAN, which even community members suggest avoiding.
If it has to be something else than .lan I would rather see .internal and not home.arpa to be honest : As soon I see ARP then I am immediately thinking it has something to do with ARP/RARP/Reverse DNS a.k.a. PTR Record for whatever reason 
I am glad that ICANN thought of .internal even tho it’s not the prettiest name out there…
For years I have been using thuis.lan which translates to athome.lan basically and so far there have been zero issues with it 