Server issues

[Sebastien Estienne]

On Nov 20, 2007 8:15 PM, Scott Kitterman <ubuntu at kitterman.com> wrote:
> On Tue, 20 Nov 2007 19:05:23 +0100 "Sebastien Estienne" <sebastien.estienne at gmail.com> wrote:
> >On Nov 20, 2007 6:10 PM, Ante Karamatiæ <ivoks at grad.hr> wrote:
> >> On Tue, 20 Nov 2007 16:15:59 +0100
> >> "Sebastien Estienne" <sebastien.estienne at gmail.com> wrote:
> >>
> >> > sebest at delly2:~$ cat /etc/default/avahi-daemon
> >> > # 0 = don't start, 1 = start
> >> > AVAHI_DAEMON_START=1
> >>
> >> But, that's not enough. Avahi (and everything done to make it
> >> usable) breaks some stuff on computers on which it doesn't even run.
> >>
> >> Best example is broken PPTP (VPN) when the other side is using .local
> >> domain. Then you have to edit /etc/nsswitch.conf and remove all the
> >> mdns stuff.
> >
> >Could you be more specific about the issue you had?
> >
> >FYI macOsX has exactly the same feature enabled by default, it's
> >called "bonjour" and the process on OsX is mDNSResponder
> >the .local is the default zeroconf domain, one common issue is that
> >microsoft also recommend to use this domain
> >"http://support.microsoft.com/kb/296250", this clashes with zeroconf
> >.local
> >
> >i think it's not specific to avahi, but to zeroconf and dns in general.
> >
> And the Microsoft one is the one the IETF standardized.  All the more reason not to install, let alone enable, it by default.

Where is the RFC that the IETF issued about .local ?

And i don't see why, microsoft is more right or wrong to use .local as
zeroconf do?
http://tools.ietf.org/id/draft-kato-dnsop-local-zones-00.txt explains
that you should use .localhost and not .local

>
> Scott K
>
> --
>
> ubuntu-server mailing list
> ubuntu-server at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
>



-- 
Sebastien Estienne