Role of DNS in Coda

of Kiss Coda Wiki

You may feel tempted to tweak client configuration to adjust a client’s behaviour to a certain Coda realm. Don’t do that. (Even clog configuration belongs to a user rather than to a host)

Every Coda client is capable of accessing every properly configured Coda realm in the world, out of the box.

The configuration burden is to be placed at the servers, which makes all the clients magically just work.

Any client is perfectly capable of figuring out which authentication- and file servers it has to talk to in each case.

A client uses the “realm” part of the file names: /coda/realm/some/thing and makes lookups based on this string.

The most important lookup is done via the global DNS service. Any reliance on client-side files like “realms”, “/etc/hosts” or a custom “/etc/resolv.conf” is incompatible with globality, avoid it. The Web is usable because each web browser is capable of talking to any web site instantly. Coda has the same quality, don’t cripple it.

This means:

Then all clients (both the ones set up by you and by others as well) will work with your realm without any additional administration.

A poor-man-alternative for a test realm with a single server may be:

Such setup based on a singe A-record may even work if you add more servers to the realm, but availability of the whole realm will depend on the first server being online.

Note1: always use the same, one and only name to access a realm. Using its servers' names or addresses may seem to work - as Coda accepts A-records as a substitution for SRV-records - however it will heavily (and possibly deadly) confuse the clients.

Note2: there is very little point in having “local” Coda realms. Coda does not rely on data being available to a certain set of client hosts, access is instead granted to identities - on any host.

At its former host this page has been accessed 507 times.

Last modified: Thu Jun 26 07:36:58 UTC 2014