Small life improvement: I have changed the domain name of my private network from ".lan" to the now standardized ".internal". So when I type <hostname>.<internal-domain> Firefox will actually access the host instead of making an internet search.
https://itp.cdn.icann.org/en/files/root-system/identification-tld-private-use-24-01-2024-en.pdf
@uncanny_static I just changed from .house to .local because IPv6 DNS... Did I choose poorly?
@falken @uncanny_static
.local is for mDNS.
* A unicast DNS service should not be configured to respond for records in that domain.
* Name resolution code should not send queries for .local to a unicast DNS server.
(see https://www.rfc-editor.org/rfc/rfc6762#section-22.1)
That's not specific to IPv6 or IPv4 either.
@prlzx @uncanny_static well, I'm announcing them either from the machines themselves or via avahi-announce (for name based virtual hosted web apps - many names same IP) so I guess is OK. IPv6 means don't need split DNS to access machines by same DNS name when in and out of home WiFi, so that was a Pi I could just turn off at same time.
@prlzx similar to my setup with FritzBox then :-)
Must get around to auto starting WireGuard on non-home wifi
@falken yes should work fine for peer-based name resolution just not a centrally managed DNS like Unbound or dnsmasq.
I have a cheap EdgeRouter (ERX) doing the DNS for the LAN (as well being a Wireguard endpoint for incoming VPN) so my v6 and v4 addresses are defined there.
When away from home, the client's DNS is overridden when the WG tunnel is up so the same FQDNs work locally and remote, which is another way to accomplish a similar outcome.