On Fri, 2016-11-04 at 23:47 +0200, Tom H wrote: > On Fri, Nov 4, 2016 at 11:26 PM, Samuel Sieb <samuel@xxxxxxxx> wrote: > > > > On 11/04/2016 02:12 PM, Tom H wrote: > > > > > > On Fri, Nov 4, 2016 at 9:58 PM, Michael B Allen <ioplex@xxxxxxxxx > > > > wrote: > > > > > > > > > > > > Of course my local network is a .local domain so it seems at > > > > least in > > > > my case mdns cannot really be used effectively. > > > > > > That's the problem. ".local" is the default mdns domain. > > > > > > You can change it by setting "domain-name=something_else" in > > > "/etc/avahi/avahi-daemon.conf". > > > > Although that would immediately make you incompatible with all the > > devices > > you're probably wanting to talk to. :-) > > If the ".local" devices that you're connecting to are served by > regular dns, it's not a problem. > this is only partly true. You loose the service discovery features of mDNS. The OP noticed that mDNS helped setting up the printer (using mDNS discovery). mDNS is nice for discovery of devices and the services they offer. It is a best practice to leave .local for mDNS. Even Microsoft recommends now against using .local https://en.wikipedia.org/wiki/.loca l offers some good information on the subject. And for DNS-domains you better use only officially registered domains, do not invent your own domain names. Somebody may register the TLD you invented. Or the IETF might define it for some special purpose. I heard of a DSL-modem vendor that used .box for local names. And guess what: somebody registered .box as an official top level domain.... Let the OP register an own domainname somewhere (or use a subdomain under a dynamic DNS name), so that the domain is somewhat formally owned. the disadvantage of the latter option is that it gives you a pretty long domain name <my-server>.<user name>.ddnsprovider.org Louis _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
