On 06.06.2017 21:59, Samuel Sieb wrote:
On 06/06/2017 12:49 PM, Walter H. wrote:so when renaming my local domain to something different, this must be sure, that not any other future bugThere are no guarantees, but at this point .lan is not likely to have any future purpose. Or if you use something unique like .waldi, you are really safe.makes me renaming it again ...
your words in gods ear ...
yes and no, when I think of some very old browsers, there could only be entered TLDs with a maximum of 4 characters, so .home and .corp could have been defined in those days for just this use case;there is a definition for IP addresses inside a LAN (RFC1918) why isn't there any definition of a TLD for just this use case?I suspect that the expectation was that everyone would just have their own domain.
but it seems that the practical intelligence is somewhere else ...
But the system is flexible enough that you can make up your own as long as you keep it private.
of course
You could even use someone else's domain as long as you won't ever want to communicate with them. :-)
this would be a goog idea as I wanted .waldi.net :-) try waldi.net, I'm sure you don't really want communicate with them ...by the way my DNS redefines e.g. the msftncsi.com in way that Windows boxes stays in LAN with these requests
(my router box also supports these NCSI files)
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
