💾 Archived View for rawtext.club › ~sloum › geminilist › 007183.gmi captured on 2024-02-05 at 10:50:41. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Carsten Strotmann carsten at strotmann.de
Wed Sep 22 11:32:34 BST 2021
- - - - - - - - - - - - - - - - - - -
Hi,
On 22 Sep 2021, at 11:36, Alice wrote:
There are registrar that disallow txt records? Lot of other services
(gitlab pages comes to mind for example) requires user to set TXT
records.
Also SPF and dkim require TXT records - and these are needed for
anyone who wants email at their own domain.
My registrar hides TXT records under an "Advanced" tab, but it's
available.
when using TXT records (which might not be the best choice for this function), they should be stored at a well-known subdomain.
The DNS currently has the problem that too many applications try to store information in TXT records on the base domain name, that creates all kinds of operational issues for the DNS service and for the applications.
For example take a look at "dig microsoft.com txt" or "dig twitter.com txt". Storing more TXT records at that place will make the situation worse.
A well-know subdomain for Gemini parameter information could be something like
_gemini_parameter.domain.tld. TXT "online-start=090000" "online-end=220000" "language=en"
Another (maybe technically better) alternative could be the new SVCB "Service binding and parameter specification via the DNS" record: <https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https>
Greetings
Carsten