This is a security issue for many devices. What could possibly go wrong overriding a tld used for internal networking....
it is not, as .local is designated as a special-use domain name and .lan is not.
It may not be an official standard, but it does have some weight as a de-facto standard.
I've tried briefly to try and find some numbers to back that up, but can't find much beyond apple's bonjour vs consumer routers - although I've seen companies with AD domains using .lan as well. (Although, I've also seen companies using 1.0.0.0/8 for their internal addressing...)
if you choose to use an unreserved domain, you are choosing to accept the risk of something like this happening. take ownership of your choices. "but other people use it" is not a great defense.
.home.arpa is so clunky. Why do I have to put the acronym of a US military project in my domain to access resources on my own local network?
Yes, I know that organization was central to the development of the l Internet, but it's not relevant as a domain 40 years later.
I've been bitten by this with my home router which uses <device>.fritz.box when somebody registered fritz.box.
This is not how anything should work.
guess I'll be migrating things 100% over to internal...
To me is a very bad idea to implement this proposal, it should instead be standardized and reserved for internal usage as a fix. There were even RFC like https://www.rfc-editor.org/info/rfc6762/#appendix-G that suggested their usage for local devices in a network.
What is the point of selling the .lan domain, except for making money at the expense of a security risk for millions of networks that already use that domain for internal hosts?
BTW to me there was never any sense to add new TLD domain despite country code. They decided to render internet less secure, by giving scammers infinite TLD to register they scam domain like "apple.lan", with the sole purpose of making for them easy money.