[Kroupware] FAQ: flexible administration of multiple kolab servers

[Brad Hards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 30 Sep 2002 15:43, Martin Konold wrote:
> This means that if the administrator decides for whatever reason (e.g.
> scalability, availability etc.) to move a user to a new machine the user
> has to be notified and needs to change settings in his client.
> For clients like OL/Bynari this is unfortunately non trivial.
SLPv2 would be much nicer, except you can't modify the client to support it.

> The proposed solution to this issue is to use the _very_ scalable DNS for
> our purposes.
There will be some people who object to using DNS. They think it is pollution. 
I am not one of them, but they are a vocal minority :)

> Basically we add for every account an A record in DNS which is pointing to
> the correct kolab server.
A record is not so nice.  You probably wanted to create CNAME records. 
Otherwise you need to change one A record per user if you have to change the 
IP on the machine. If you just have CNAMEs for users, you only need to change 
it once.

If you have client support (probably not), you can use SRV records (SRV2052), 
maybe even in conjunction with PTR records (see http://www.dns-sd.org for an 
old Internet Draft). This is basically what Apple Rendezvous does.

> 2.  In addition the administrator can much more easily move users to
> different servers in a transparent manner.
With Dynamic DNS, you can do this automagically from the LDAP server. 

- -- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Aust. Tickets booked.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9l/l9W6pHgIdAuOMRAsZyAKCWYxna46TrFBi/YwKKOJeYeDcvjQCfcQw2
kV0s4xQAFfDqs3CnFjxplfs=
=+4Hh
-----END PGP SIGNATURE-----