[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon

[George]

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
Foundations Bugs, 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 at 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