For those of you who might want to keep using the provider's name
servers; Change the value of AVAHI_DAEMON_DETECT_LOCAL, which is located
at /etc/default/avahi-daemon, to zero.
and the error message disappeared.
If somebody, who knows well how this part of the system works, would like to write a small description
about, it might be nice.
----- Original Message -----
> From: Sebastian Salvino <firstname.lastname@example.org>
> To: email@example.com
> Sent: Monday, July 1, 2013 6:15 PM
> Subject: Re: it is avahi? Re: network
> on 7/1/2013 10:35 AM Daniel Landau said the following:
>> On 2013-07-01 16:07, Matus UHLAR - fantomas wrote:
>>> On 01.07.13 15:56, Daniel Landau wrote:
>>> Could you please go to General Screen as mentioned on page 179, section
>>> Is the domain set to .local? What happens if you put back your ISP DNS
>>> servers but change domain name to something different? (iki.fi,
>>> or something).
>>> It should work flawlessly imho.
>> The domain is set to zyxel.com. I changed it to landau.fi (which I
>> control), but this didn't have any noticeable effect. If I change the
>> DNS to ISP the error returns.
>>>> However, with my previous router, I could connect to machines on my
>>>> wireless network* using their hostnames (which is e.g. useful for
>>>> moving files to/from Android devices wirelessly with ftp), now I
>>> I guess this might be one of issues using .local in your network
>> It doesn't seem to be related. With my old router (a Wippies HomeBox
>> http://forum.wippies.com/wiki/Wippies_HomeBox) my resolv.conf contains a
>> line "search Sauna". With the ZyXEL router there is a line
>> zyxel.com" or "search landau.fi" depending on the setting.*
> If I instead
>> put .local in that spot, my resolv.conf doesn't have a search line. I
>> think the "search Sauna" thing would seem to mean, that the
>> router is doing something active to ensure that the hostnames resolve
>> correctly. If I get a pointer to some material, I'd be happy to set up
>> local DNS server to resolve my local hosts.
>> Daniel Landau
> The Avahi issue that some of you were experimenting was not related to
> customer's side but provider's side.
> For those of you who might want to keep using the provider's name
> servers; Change the value of AVAHI_DAEMON_DETECT_LOCAL, which is located
> at /etc/default/avahi-daemon, to zero.
> To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> Archive: http://lists.debian.org/51D19D26.firstname.lastname@example.org
To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com
Archive: 1372746024.33707.YahooMailNeo@web161301.mail.bf1.y ahoo.com">http://lists.debian.org/1372746024.33707.YahooMailNeo@web161301.mail.bf1.y ahoo.com