2 ms·
> , and have their content available to the rest of the web. The issue is that DNS and registrar services are fragmented by design, and there doesn't seem to b
by judge2020 5y ago
> , and have their content available to the rest of the web.
The issue is that DNS and registrar services are fragmented by design, and there doesn't seem to be a standard DNS API that would make it easy to simply say"select your domain registrar" and use that to start an oauth flow then manage DNS records for a site. Therefore, anyone who does run even a simple service like hosted wordpress (without using the host as their registrar) needs to at least have basic knowledge of what DNS records are and how to put in their registrar without messing up email records or other subdomains they might have.
- anderspitman 5y agoThere's the DomainConnect protocol[0] which has been around for a few years. I didn't find it particularly well matched for open source projects, so I've also done some work on my own protocol[1]. The current draft is implemented by TakingNames.io (as a provider) and boringproxy (as a client). You can read more about it and watch a demo here[2]. That said, I think DNS might not be the right layer of abstraction to simplify this. I think we need an open tunneling protocol[3]. [0]: https://www.domainconnect.org/ https://www.domainconnect.org/ [1]: https://github.com/takingnames/namedrop-protocol-spec https://github.com/takingnames/namedrop-protocol-spec [2]: https://takingnames.io/blog/introducing-takingnames-io https://takingnames.io/blog/introducing-takingnames-io [3]: https://forum.indiebits.io/t/toward-an-open-tunneling-protocol/30/1 https://forum.indiebits.io/t/toward-an-open-tunneling-protoc...