Oh I see, I'm so engaged in solving the problems with Avahi not running so I interpreted "I am blessed with a unicast .local domain." as an ironic statement, sorry for that... :) - but now I got Avahi working again with help of the procedure described on www.opendns.com. This made my DHCP configuration work again, combined with some effort in defining host and domain names provided from my ISP, which I put into my router (Linksys WRT54GS). Command host -t soa local returned Host local not found: 3(NXDOMAIN) just as you said, so I think I will stay by that for now. In some cases I could find it practical to use static IP addressing though, so I might try it again sometime. Right now I put more value to my mtdaap server on my NAS. This gives me also some doubts to if the widely written avahi problem really is a bug, or if it maybe is more of a case of difficulty-to-tell-how-it-works... Thanks for leading me in another direction anyway!
Cheers, Ola -- Race between avahi-daemon startup by dbus and .local check in if-up.d https://bugs.launchpad.net/bugs/111834 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
