Public bug reported: I know this has been reported before, and always flagged as Won't fix, but I think this really deserves at least a look.
Problem: A user purchases a new Ubuntu computer is shipped with zeroconfig enabled, brings it to work and plugs it into the network that has been configured using Microsoft's recommendation (http://support.microsoft.com/kb/296250) for domain names (hostname.domainname.local) and it won't resolve local hosts. The user is not a computer geek (he called me for that), and he can't figure out what's wrong. A quick rearrangement of the nsswitch.conf fixed the problem, but the average user would have just followed the recommendation of their IT dept. and switched to Windows. Even though .local has been reserved as the "domain name" not the "extension" for hosts on a zero config mDNS network . . . Is there any reason why hostname.domainname.local can't resolve to unicast DNS? I've spent hours reading the specifications, and don't see why this isn't possible. So: hostname.local = Multicast DNS hostname.domainname.local = Unicast DNS This should work with both Microsoft's recommendation and with Zeroconfig. ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- zeroconfig breaks hostname.domainname.local https://bugs.launchpad.net/bugs/153644 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
