[Leaplist] avahi

[Dan Cherry]

Thanks Hank & Kyle,
I don't have an immediate need for avahi, so I'm running disabled for the time 
being.  I'll plan to change my internal domain to something other than .local 
so I have the option for avahi (or OSX) down the road.

I went through the bind files, and will have to sift through which references 
to "local" are for my domain name, and which are for the reserved 
word "local" used by bind.  I liked the suggestion of going to .loc since 
there would be less confusion over which words are data, and which are 
control.

Thanks,
Dan


On Sunday 28 October 2007 5:44:56 pm Kyle Gonzales wrote:
> This is because Avahi in Linux/BSD desktops and Bonjour in Mac OS X
> are both implementations of the Zeroconf standard.  To do some light
> ready about the Zerconf standard:
>
> http://en.wikipedia.org/wiki/Zeroconf
>
> For heavier reading:
>
> http://www.zeroconf.org
>
> Zeroconf makes use of the .local extension.  Any network where a
> Zeroconf implemetation is in use will have problems if the .local
> extension is already in use.
>
> If you are content to run networks the way you have been, you can
> disable Avahi.  However, many new desktop sharing featues (like
> sharing songs between Rhythmbox, iTunes, and others) require an active
> Zeroconf implementation.
>
> On 10/28/07, Hank Lambert <hank at hanklambert.com> wrote:
> > I'm not sure what Avahi is, but it isn't the only one that is starting to
> > have problems with the .local extension. Mac OS X has problems with
> > networks that uses a .local extension. On the networks we are installing,
> > we started using .loc instead of .local because we have clients who use
> > Mac's for graphics, and when they upgraded to OS X, they could no longer
> > connect to the network.
> >
> > Hank Lambert
> > KB4MTO
> > Certified Geek
> >
> > -----Original Message-----
> > From: leaplist-bounces at leap-cf.org [mailto:leaplist-bounces at leap-cf.org]
> > On Behalf Of Dan Cherry Sent: Sunday, October 28, 2007 1:34 PM
> > To: LeapList
> > Subject: [Leaplist] avahi
> >
> > Hi,
> > After upgrading Kubuntu Feisty to Gutsy, I got burned by Avahi, and it's
> > limitation on using ".local" as a local domain on my intranet.  (It's
> > been ".local" for about 6 or 7 years, and never been a problem 'til now).
> > Seems the specific name ".local" is a no-no for Avahi, which isn't the
> > end of the world, but most configured references to various machines on
> > my internal network, now fail.  Seems like I've got three options (and
> > would welcome other suggestions as well).
> >
> > 1)  Change all the references to xyz.local to xyz  (removing the .local,
> > which avahi apparently defaults to - and I'm not sure if that will handle
> > all the references or not)
> > 2)  Change the internal domain from ".local" to something else, such as
> > ".lan" or ".home" - which means changing all the references and my bind9
> > config files - and maybe more...
> > 3)  Don't run Avahi, and change nothing else - that's working at the
> > moment.
> >
> > Any advice or warnings about which way to go?



-- 
Dan
Finding a solution to a problem doesn't solve the problem...
Implementing the solution, solves the problem