[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
Trent: Wow, thank you! I switched away from that problematic ISP in 2017 but I'm glad it'd now function correctly by default. George: You can file a new bug at https://bugs.launchpad.net/ubuntu/+source/nss-mdns unless there's already a bug about it, and link the github issue also there. ** Also affects: nss-mdns (Ubuntu) Importance: Undecided Status: New ** Changed in: avahi (Ubuntu) Status: Confirmed => Invalid ** Changed in: nss-mdns (Ubuntu) Status: New => Fix Released ** Changed in: nss-mdns (Ubuntu Karmic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Invalid Status in nss-mdns package in Ubuntu: Fix Released Status in avahi source package in Karmic: Won't Fix Status in nss-mdns source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
Discussion on this new issue: https://github.com/lathiat/nss- mdns/issues/75 ** Bug watch added: github.com/lathiat/nss-mdns/issues #75 https://github.com/lathiat/nss-mdns/issues/75 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
After some more searching I found an explanation of this issue in Ubuntu 20.04 and the correct way to disable it: https://github.com/lathiat/nss- mdns#etcmdnsallow -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
It seems not "fixed", but rather broken again in Ubuntu 20.04. My ISP DNS servers respond to all ".local" queries with "127.0.0.200", and mDNS just doesn't work in this case. Setting AVAHI_DAEMON_DETECT_LOCAL=0 does not help. This is regression from 18.04 where mDNS worked fine with default settings. And it's a pity, as mDNS is even more important after NetBIOS/SMB1 retirement in 20.04. Should I post details here or start a new issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
That's great! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
For anyone looking at this in 2020, this is fixed in nss-mdns 0.14 which is in Ubuntu Focal 20.04 - it will now correctly pass through unicast .local lookups. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
** Summary changed: - Order Ambien Online to Manage Irregular Sleep-Wake Rhythm Disorder + Some ISPs have .local domain which disables avahi-daemon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
As I found this bug accidentally after years, just small remark: a) The firm I work for keeps naming hosts in internal network «name».ourfirm.local. Those addresses are omnipresent (from network config to myriads of development/test/staging/whatever environments and config files), so advice to abandon them is unlikely to be considered. Ah, and we started our naming convention in 1997 or so. Zeroconf was born in 2002 on Mac, appeared on Linuxes around 2007-2010, and was RFCed in 2013 :-P b) Still, this simply means that our „linux installation checklist” contains request to edit /etc/nsswitch.conf and remove mdns4_minimal [NOTFOUND=return] Having said that, I still have no clue why avahi couldn't restrict itself to non-dns-resolvable addresses and leave those resolvable to DNS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
This is *still* a problem on 16.04.1 LTS. This message in syslog: Dec 5 14:12:11 tali avahi: Avahi detected that your currently configured local DNS server serves Dec 5 14:12:11 tali avahi: a domain .local. This is inherently incompatible with Avahi and thus Dec 5 14:12:11 tali avahi: Avahi disabled itself. If you want to use Avahi in this network, please Dec 5 14:12:11 tali avahi: contact your administrator and convince him to use a different DNS domain, Dec 5 14:12:11 tali avahi: since .local should be used exclusively for Zeroconf technology. Dec 5 14:12:11 tali avahi: For more information, see http://avahi.org/wiki/AvahiAndUnicastDotLocal There is no .local domain: ~ • host -t SOA local ;; Warning: Message parser reports malformed message packet. local.Home has no SOA record ~ • host -t SOA local. ;; Warning: Message parser reports malformed message packet. local has no SOA record (Some posts I found do the lookup with a trailing dot, others omit it, so I did both.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon Status in Release Notes for Ubuntu: Fix Released Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Karmic: Won't Fix Bug description: Binary package hint: avahi-daemon After a fresh install of Jaunty Alpha 3 avahi did not work and as a result of that - not Bonjour in Pidgin, and some network discovery stuff. I have been looking for a solution, but still - after the fresh install, when I used Intrepid, it worked fine. During boot I see some error with avahi-daemon (do quick to actually read), and I think that it is the same thing as I get when trying to startup avahi-damon: daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon * avahi-daemon disabled because there is a unicast .local domain And after login there is a notify regarding the same matter. This same things is confirmed on my finances netbook. We used the Alternative Jaunty CD for install (due to that the install crashed when the installing user already existed in /home, on the desktop CD) Awesome work - keep it up! ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
