Difference between revisions of "Alt root"

From Cibernética Americana
Line 9: Line 9:
<div style="background-color: grey; color: white;">
<div style="background-color: grey; color: white;">
<div style="position: relative;left: 40px;text-align: left;width: 500px;">
<div style="position: relative;left: 40px;text-align: left;width: 500px;">
  <span style="position: relative;left: 5px;> [[File:KASTALIEN.svg|left|thumb|125px|[https://sameboat.live Go There]]]</span>
  <span style="position: relative;left: 5px;> [[File:KASTALIEN.svg|left|thumb|125px|[http://sameboat.dom Go There]]]</span>
<h1 style="text-align: center;font-weight: 900;">.dom</h1>
<h1 style="text-align: center;font-weight: 900;">.dom</h1>
<h5 style="text-align: center;">Domain Engineering TLD</h5>
<h5 style="text-align: center;">Domain Engineering TLD</h5>

Revision as of 11:09, 13 January 2020

Alt-rooted means that an autonomous name system distinct from just the priced IANA system alone is in use.[1] Beginning in 2019, a migration of virtually all content in my dev space, with the exception of a few necessary public pages, is in process: all content is going to be alt-routed, either same named, ICANN TLD -> .dom, or the ICANN/IANA TLD just dropped. As used here refers to an autonomous peerage that routes TLDs upon discretion of the operators. A reasonable effort for a free service level is committed that just works by:

adding the following name servers, which are non-recursive, in desired order to your active resolver(s):

  • ns0.<IANA_TLD>
  • . . .
  • ns<n>.<IANA_TLD>

where «IANA_TLD» is the priced system transfer domain and, <n> is currently 1, or their ip addresses if your resolver requires it and where

use the designated <IANA_TLD>

  1. Neustar meansofproduction.biz thru May 2019*;
  2. Donuts sameboat.live thru October 2021;
  3. Then, different two-level public name(s), for n years posted here with n.

* And until March 2020 or longer but not for the inter-TLD purpose.

Paid²[2]users have access from recursion and additional basic name services for users below developer class up to continuous live maintenance by intelligent agency for operators.

As used here, the background operation of the public priced name systems are assumed as needed, excluded where desirable, e.g. for privacy or security. Our system is constructed using the standard unix networking software and forms a superspace of the public name system with these properties:

  • Individual operators of the system determine which TLDs they recognize. The system administered here only allocates the TLDs FCFS to operators, it doesn't have the intent of acting as a sole authoritative source even for the .dom name, which operators may override to establish cooperating alt roots. The TLD operators in essence agree to a common real TLD space which they may present internally differently, but which starts with the common public systems plus a single reserved name: ".dom" for their private/peer namespace.
  • IPV6 and TLS are defaults, 4 and plain text special cases.
  • A rich default common systems application environment which operators may optionally use is provided in which all users are identified and at least in principle, traceable.

An equivalent function is assumed for peer operators, as provided by my DNS/EPP tooling merged with the FRED Czech NIC software as maintained by me for my Ubuntu LTS targets. End users of the "sameboat/C-六" core PHP-Python CMS have significant consumer level DNS functionality upon sufficient entitlement.

  1. see Alt root
  2. Price for the full SaaS without any physical resources other than control and delivery bandwidth kept under 10 工 per TLD quarter assuming only stability of fiat basket basis of the 工.

³ "clean" means a newly formatted host OS instance; Our modifications of various elements such as letsencrypt included in the SaaS, woven through various process such as SSO, registration, etc.