[Leaplist] avahi

[Richard F. Ostrow Jr.]

Hmm...

On my network, this would be a minor problem:

Step 1 - adjust DHCP config to assign domain name to something else
Step 2 - adjust BIND to the new domain name
Step 3 - DHCP renew (or just let the lease renew on its own) each client
machine.

Fixed.

Not sure if such is reasonable on your network, but on mine I like having
a single point of configuration so I don't have to go around individually
configuring each machine.

Consequently, I propose option 4 - Add DHCP support to each machine for a
centralized configuration system. It takes more effort up front, but will
likely reduce your level of pain at some point down the road.

Otherwise, I'd stick with option 2. If you simply used host names in your
other config files, your domain of .lan or .home would automatically be
appended and everything should "just work".

Either way... good luck.
-- 
Life without passion is death in disguise

On Sun, October 28, 2007 1:34 pm, Dan Cherry wrote:
> 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?
> Thanks,
>
> --
> Dan
> Finding a solution to a problem doesn't solve the problem...
> Implementing the solution, solves the problem
> _______________________________________________
> Leaplist mailing list
> Leaplist at leap-cf.org
> http://lists.leap-cf.org/mailman/listinfo/leaplist
>