Public bug reported:
My ISP provides a .local-domain in their DNS config. The only thing i've
been able to find, is a ".local" A-record that points to 127.0.0.1.
Silly, I know, but ISP:s can be like that.
This gives me some head-ache in regards to Avahi. Whenever I login,
avahi (or possibly the service-discovery-applet) sends out a popup,
telling me that a previous unicast .local domain was discovered, that
this was bad, and that Avahi disabled itself.
Fair enough, I can live with that I have to fiddle with it, set up my
own caching NS when my ISP don't do it right, etc. However if I don't
deal with the situation, (I.E. own caching NS) an hour so later, the
message pops up again. I suspect it's got something to do with DHCP
lease timeouts, triggering something. I think a less understanding user
would have a problem with this.
What I would like to happen instead; (2 alternatives)
A) Avahi handles the situation, and tries to use both the mDNS .local-domain
and the pre-existing .local-domain. Sure, it might imply some
hard-to-troubleshoot conflicts, but in most cases it'd probably work as
expected.
B) Avahi detecting the problem, telling me about it as it does now,
offering me a link where I can find more information, as well as a good
argumentation to throw at my ISP, and a "shut up" option, that makes the
popup go away and stay gone.
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Avahi behaves badly where there is a unicast .local-domain.
https://launchpad.net/bugs/83468
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
