On 8 Jul 2024 01:03 +0200, from ay...@fsfe.org (David Ayers): > Hello everyone! > > My Debian 12/bookworm laptop uses DHCP with NetworkManager which > produce an /etc/resolv.conf containing: > # Generated by NetworkManager > ``` > search home > nameserver 192.168.1.254 > ```
Note that .home is somewhat of a special snowflake with regards to TLDs. It was suggested as the default for HNCP in 2016 (RFC 7788 section 8 <https://www.rfc-editor.org/rfc/rfc7788#section-8>); rejected as a gTLD in 2018 <https://www.icann.org/en/board-activities-and-meetings/materials/approved-board-resolutions-regular-meeting-of-the-icann-board-04-02-2018-en#2.c>; and then the usage from RFC 7788 was effectively superceded by the recommendation and assignment for non-unique use of home.arpa a few months later in RFC 8375 <https://www.rfc-editor.org/rfc/rfc8375>. This may or may not have anything to do with your issues; but in general, making up own TLDs and hoping that they will never conflict with public ones is a bad idea these days. Just look at how many internal names suddenly started having issues after Google was assigned .dev in 2019; to say nothing of that they made it a preloaded-HSTS TLD. It's better to either use .home.arpa (which is specifically reserved for the purpose) or to actually register a domain (even if the name server delegations are bogus so it never meaningfully resolves on the public Internet). -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
