Bug 5599 - Support SRV records to find server address
Summary: Support SRV records to find server address
Status: CLOSED WONTFIX
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.15.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-29 09:28 CEST by Karl Mikaelsson
Modified: 2023-05-16 13:44 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Attachments

Description Karl Mikaelsson cendio 2015-07-29 09:28:46 CEST
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.
Comment 1 Pierre Ossman cendio 2015-08-10 14:38:31 CEST
(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.
Comment 2 Karl Mikaelsson cendio 2016-10-19 10:07:42 CEST
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 user@domain.local 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
Comment 4 Pierre Ossman cendio 2023-05-16 13:44:58 CEST
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.

Note You need to log in before you can comment on or make changes to this bug.