On 06/06/2017 12:49 PM, Walter H. wrote:
On 06.06.2017 20:27, Samuel Sieb wrote:
Either you've been lucky or those other systems don't support MDNS yet.
given the possibility that the strange phenomens mentioned in the OP are
really caused by using .local as my intranet-TLD,
then why doesn't nslookup of the Fedora box tell me errors or whatever,
when doing just
nslookup proxy.local?
nslookup only does direct DNS, it doesn't use the system resolver.
so when renaming my local domain to something different, this must be
sure, that not any other future bug
makes me renaming it again ...
There 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.
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 the system is flexible enough that you can make up your
own as long as you keep it private. You could even use someone else's
domain as long as you won't ever want to communicate with them. :-)
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
