New feature: zeroconf networking by default, please test

[Martin Pitt]

Hi Ulrik,

Ulrik Mikaelsson [2007-01-02 14:02 +0100]:
> My ISP:s DNS servers replies on queries to the .local-domain, with an
> A record, pointing to 127.0.0.1. This confuses avahi-daemon, that
> shuts down. 

It's not really 'confusion'. Since the RFCs explicitly reserve
'.local' for Zeroconf usage, having an unicast (i. e. 'normal' DNS
network) '.local' domain is not recommended. In order to not loose
access to that unicast .local domain, avahi shuts down itself so that
it does not shadow it with the zeroconf .local network. This was done
on purpose.

> The problem is though, it seems to restart itself after a
> while, only to detect the problem again, and shut down.

We live in a network roaming world, thus each time you get a new DHCP
lease, the check is done again. So the interval depends on the length
of the DHCP lease time.

> How shall this be dealt with? Personally I've setup a local forward
> DNS and at the same time filed a complaint to my ISP, but I guess
> neither will my ISP care, and the average user wouldn't even know what
> to do in this case.

Well, I hope that unicast .local domains are not that common and will
gradually disappear. I also do not want to entirely disable Avahi for
all times when you just happen to walk into a WLAN with a .local
domain somewhere. A compromise would be to leave the current
autodetection magic, but not show the notification more than once per
session. What do you think, would that be better for you?

Thanks,

Martin

-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20070112/dc95374b/attachment.sig>