It would be neat if the client could look up SRV records for, say, _thinlinc._tcp.example.com, and find out where the master server is located. You could then set the clients to connect to "example.com" and they'd figure out the rest from there.
If the client was extended so to try all servers in the SRV records, a HA setup without keepalived would be possible.
(In reply to comment #0)
> If the client was extended so to try all servers in the SRV records, a HA setup
> without keepalived would be possible.
A client already tries all A/AAAA records today. But such an approach can cause long delays if the downed master isn't returning an error quickly. Hence it is not a very good replacement for keepalived.
We got another similar idea from a customer:
> I think this one would be cool:
> - Allow users to login only by entering their email in the client (no need for setting ports or server addresses)
> How it would work:
> - User enters firstname.lastname@example.org in the client (nothing more)
> - Thinlinc client would query a SRV record for _thinlinc._tcp.domain.local
> - DNS can return the thinlinc fqdn and port (standard feature)
> - Thinlinc client would configure the values and connect
There is no clear use case here so let's close this until we get some actual user request where we know what problem needs to be solved.