About Sameboat DNS

Basic knowledge of what DNS is is assumed

Domain Space (DS) provides a name service on a class basis to end users and to operators running their own TLD like my .dom (free non-recursive use instructions in link). Ultimately, to use the parts of DS not in the wild, you will have to exercise control of your namespace which may seem to be blocked by your existing network provider layering. At some level this is very simple, most users are unaware of the name system and even technical users generally take it for granted. This simplicity is partly real, at least at the end user level, and partly an illusion created by various interests to give you a seamless experience of the internet.

A simple test of the minimal degree of control on a given host is the ability to ping, e.g. sameboat.dom and reliably get a response from an alt server rather than only nameservers set by your ISP, help for which will be available eventually in the conversational help facility¹. Typically dhcp is a source of overrides/resets which need not be obstructive, however replacing dhcp with a static link to your ISP once the link parameters are known may be a brute force solution. DS augments rather replaces the public name system with a peer-peer extension and its smooth operation should make the difference largely transparent to authenticated users.

DS end users, who may range from casual non-technical users to developers, are not selling names and are not operating as either a registrar or registry. They may get and use names in the .dom alt system or the regular public name system and mixing the two is the modus operandi for separating public facing production and private, e.g. development, intranet, etc, domains. Operators are registrars in .dom, and can be peer registries if they choose to operate in my alt-root scheme, which supplements rather than replaces the regular name system, as closed private TLDs, etc. To use a name gotten from a registry in the regular name system, such as google domains, for general use other than as a linking domain, you must be able to set its name servers to DS servers and manage the name though them.

Sameboat Managed

sameboat currently uses the .live suffix for public access to sameboat.dom

  • Each network node is a first level subdomain, canonically the geonode's, e.g. bufyyz. Unified IRC channels are subdomains of irc.sameboat .
  • Other names are mostly allocated freely FCFS with some namespace reservations for system purposes .

Domain Owner Function

These services are available to current akperson accounts:

  • Get a zone in the .dom TLD which is not taken by another end-user or delegated to an Operator.
  • Manage their zones, including both .dom and those of common public registries such as those of ICANN/IETF.
  • Manage DNS functions on Linux, MacOS or Windows hosts to get started using the .dom TLD or own their local DNS.

    These extended services are bundled with various priced offerings:

  • Use domain engineering functions that presume DNS ownership.
  • Operate some enterprise or organization as a managed domain application via hosting at supported vendors with automated provisioning from the .dom TLD. SKUs bundling AWS and Linode are available but any hosting service with current debian/ubuntu will work if you have full operator access to the .dom software.

Registry/Registrar Function

An Equity class user with operator session role can run their own instance(s) of some or the entirety of my domain space supporting software. Minimally this includes the full DNS system program complement coordinate with my root via EPP mechanisms as done in the '14 job. Optionally ...

  • Use domain operator level domain knowledge engineering functions as they are rolled out.
  • Operate as a registrar in my alt root. Each DNS Operator selects a single which is either "dom" or an available Kastalien TLD. If it is "dom" then the Operator is running an independent alt-root, which is supported and termed "non-cooperating". Cooperating Operators work within their single TLD or negotiate with me a name space entitlement analogous to the situation in the public name space.
  • Operate a registry. I have adapted the Czech national DNS (FRED) for domain space and accounts eligible for operator session role include an optional FRED setup. Cooperating Operators can and non-cooperating Operators must (in order to be supported) operate a registry. Most registrars will want to avoid the burden of managing the FRED software and just use the .dom EPP services..

DNS registry/registrar entitlements are distinct from those that default to Developer or Operator AKPERSONs.

¹ web search on resolvconf should help on unix, the advice given in the pop-ups for KASTALIEN when you select thoughtcrime domain on the README may suffice.