Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using SRV records instead of requiring custom server specification #2682

Closed
madduck opened this issue Dec 3, 2016 · 3 comments
Closed

Using SRV records instead of requiring custom server specification #2682

madduck opened this issue Dec 3, 2016 · 3 comments

Comments

@madduck
Copy link

madduck commented Dec 3, 2016

I should be able to log in to Riot.im with username madduck@madduck.net or @madduck:madduck.net and expect the app to to a SRV lookup on the domain to figure out the homeserver to use. Expecting users to specify a string like https://matrix.madduck.net:8448/ as "custom server" (which also requires several clicks and Javascript-roundtrips) is not particularly user-friendly.

@richvdh
Copy link
Member

richvdh commented Dec 5, 2016

browsers don't support SRV lookups, so this is not possible. One option would be to support a .well-known file, which is tracked at matrix-org/matrix-spec-proposals#433.

@jonas-hagen
Copy link

Would it be possible to use DNS-over-HTTPS? This specification attempts to solve exactly this problem. Possible providers would be Google and Cloudflare.

Example:
curl 'https://cloudflare-dns.com/dns-query?ct=application/dns-json&name=_matrix._tcp.matrix.org&type=SRV'

Also see: Mozilla Is Testing "DNS over HTTPS" Support in Firefox (it uses the 1.1.1.1 Cloudflare DNS server for DNS-over-HTTPS)

@t3chguy
Copy link
Member

t3chguy commented May 25, 2018

@jonas-hagen that means exposing your privacy to that provider. Plus the SRV is used only to specify the location of fed api and not client api, they don't have to be the same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants