💾 Archived View for rawtext.club › ~sloum › geminilist › 001997.gmi captured on 2020-09-24 at 03:26:42. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

SRV records

Carsten Strotmann carsten at strotmann.de

Sun Jun 28 10:14:07 BST 2020

- - - - - - - - - - - - - - - - - - -

Hi Evert,Hi List,

Evert Pot <me at evertpot.com> writes:

It occurred to me that it would be nice if I could use DNS SRV

records

to point gemini:// clients to a different host. However, after

reading

the spec it doesn't seem like there is support for this.

The SRV record might be superceded by the SVCB/HTTPSSVC record:

Service binding and parameter specification via the DNS (DNS SVCB and HTTPSSVC)<https://tools.ietf.org/html/draft-ietf-dnsop-svcb-httpssvc>

Goolge is experimenting with this to be able to upgrade HTTPS sessionsto QUIC, while Apple seems to use it to discover DoT/DoH resolver forthe upcoming MacOS 11 and iOS 14.

SVCB/HTTPSSVC is an Internet Draft, it will likely change (a lot) untilreaching RFC status, or it might expire (not reach RFC status at all).

The problems remains that OS resovler libraries (libc) do not support DNSrecords other than A/AAAA and a handful of others.

Libraries like GetDNSAPI <https://getdnsapi.net/> need to be used to retrievethese records.

Gemini server discovery could be discussed in a document separate of theGemini protocol spec.

Client implementations could optionally implement support for findingGemini server via SRV, SVCB, mDNS or other discovery protocols.

Greetings

Carsten