About Sameboat DNS
Knowledge of what DNS is assumed below
Ultimately, unless it is done for you, to use an alt/aux name system, 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. The reality of efforts to control your namespace will become apparent once you try to control it yourself, unfortunately there's no single point of control to set, or even a scope, that will allow you this control in a clean and simple way. For example most (but not all) browsers will try to establish control even if you have made a name pingable at the command line in the browsers host OS. Fortunately, applications in general will operate as expected once you've made a name available at the OS level. We attempt to make as easy as possible but you need to be aware of the real situation or you should probably avoid alt name spaces all together and rely on control of your namespace by the powers that be. Those powers include us if you use our systems and we insure that core space names are available to our provisioned hosts and deployed apps.
DS end users (non-O class), who may range from casual non-technical consumers to devops users, are not selling names and are not operating as either a registrar or registry. They may get and use domain spaces names and combine them with names from the regular public name system in our aux root to form private spaces without becoming domain space operators. Operators are registrars in .dom, and can be peer registries if they choose, 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.
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.
Non-devops users are only expected to understand the above about DNS. Like the interests mentioned above DS attempts to make augmenting public namespace with a private extension easy/simple including support by discursive agents that will talk you thru the needed actions.
The Domains CMS Network and Name Space
sameboat .live suffix will be dropped after October 2022
- Nodes are first level subdomains, canonically the geonode's, e.g. bufyyz.
- Other names are allocated FCFS as in the general public namespace (but distinct from it) with some names reserved by the central system .
- System reserved name restrictions will in effect be a lesser effect than that of commercial and jurisdictional squatting in the public system.
These services are available with a current standard entitlement to all AKPERSONs:
- 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.
An AKPERSON with operator privilege can run their own registry or act as a registrar. Minimally this includes the full DNS system program complement coordinate with my root via EPP mechanisms first worked in the '14 job. An operator selects a single governing TLD for each domain space which is either "dom" or an available Kastalien TLD. If it is not "dom" then the Operator is running an independent name system, which is supported and termed a "peer domain space" which may be co-operating with core domain space as a separate registry or not. If the TLD is .dom the operator is a registrar only within .dom. Optionally ...Note that registrars and registries can manage their public (IANA) names with our name services.
- Use domain operator level domain knowledge engineering functions as they are rolled out.
- Operate as a registrar in my alt root.
- Operate a registry. A Peer Operator can be cooperating with our system or just using the software independently in which case they are termed non-cooperating. I have adapted the Czech national DNS (FRED) for domain space and accounts eligible for operator session role include an optional FRED setup. Non-cooperating peer operators are supported for the software distribution service only. Most registrars will want to avoid the burden of managing the FRED software and just use the .dom EPP services.
Participation in .dom is not a priced entitlement. Operators are subject to oversight and in cases where overall health and integrity of the TLD could be negatively affected, this privilege can be withdrawn. Operators that cannot or do not wish to comply should run their own TLDs .
¹ web search on resolvconf should help on unix, the advice given in the pop-ups for KASTALIEN names when you select them on the README may suffice.