This can be done in two ways. The first way will find default servers. This will enable clients with no configuration to use this server. The distributed elvind.conf does not set default to prevent casual installations disturbing the local Elvin deployment. You can use automatic service discovery with a scope name .
Scopes are orthogonal to default-ness.
They allow clients to select a server from a configured pool of servers, for example, provisioned for a particular application. It is not necessary to specify a scope, but note that unless either a scope name or default is configured, the server cannot be discovered automatically. Client connections can be configured to use discovery with a scope name. Only one scope name may be used, and the use of default is not compatible with scopes.