From e0c315ef096f6aea0b0f9ad410985a495fb8bbb8 Mon Sep 17 00:00:00 2001 From: netkas Date: Mon, 2 Sep 2024 20:14:53 -0400 Subject: [PATCH] Rename 'DNS Handshake' to 'DNS Records'. --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 8a821eb..2fdb005 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ This project is licensed under GNU Free Documentation License v1.3, see the [LIC * [Table of contents](#table-of-contents) * [Specifications](#specifications) * [UUID v4](#uuid-v4) - * [DNS Handshake](#dns-handshake) + * [DNS Records](#dns-records) * [Peer Address](#peer-address) * [User Address](#user-address) * [Server Address](#server-address) @@ -104,7 +104,7 @@ consumed for the variant. Source: [Wikipedia](https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_4_(random)) -## DNS Handshake +## DNS Records When a client wants to connect to a Socialbox server, it first needs to perform a DNS handshake to discover the server URL. Typically, the Socialbox server is hosted on a subdomain like socialbox.example.com. To determine this, the client @@ -200,7 +200,8 @@ standards. Below are the modifications made to the JSON-RPC 2.0 specification: To host an RPC server, you must configure your domain name to have a subdomain that serves as the RPC endpoint for your Socialbox instance. For example, if your domain is example.com, you can host the RPC server on the subdomain socialbox.example.com. The RPC server should be accessible via HTTPS, and the root URL should be the RPC endpoint. For -example, the client would assume the RPC endpoint URL would look like this after preforming the [DNS Handshake](#dns-handshake): +example, the client would assume the RPC endpoint URL would look like this after preforming the DNS Handshake, see +[DNS Records](#dns-records) to see how this part is configured. ```text https://socialbox.example.com/