On 06.06.2017 20:27, Samuel Sieb wrote:
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 justOn 06/06/2017 11:22 AM, Walter H. wrote:Either you've been lucky or those other systems don't support MDNS yet.On 06.06.2017 20:13, Samuel Sieb wrote:this works on all systems I have even with .local in my DNS except with this Fedora;On 06/05/2017 11:27 PM, Walter H. wrote:On Tue, June 6, 2017 07:40, Samuel Sieb wrote:On 06/05/2017 10:19 PM, Walter H. wrote:p.s. in case the phenomenas of the OP won't change these are true bugs.I don't understand what you're saying here.the system/Firefox has to take e.g. proxy.my.lan as proxy server ... also the printer must work with e.g. lpd://printer.my.lan/CP1515N ...and not just with the IP address ...That should all work. The problem you are having is that you are using .local in your DNS.sounds strange ...
nslookup proxy.local?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 is a definition for IP addresses inside a LAN (RFC1918) why isn't there any definition of a TLD for just this use case?
Greetings, Walter
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
