Difference between revisions of "Alt root"

From Cibernética Americana
Line 2: Line 2:
 
<!--
 
<!--
 
function popitup(url) {
 
function popitup(url) {
newwindow=window.open(url,'name','height=600,width=450');
+
newwindow=window.open(url,'name','height=600,width=450;');
 
if (window.focus) {newwindow.focus()}
 
if (window.focus) {newwindow.focus()}
 
return false;
 
return false;
Line 10: Line 10:
 
<h3 style="position: relative;top: 5px;left: 10px;">Alternative domain name system&sup1;</h3><br>
 
<h3 style="position: relative;top: 5px;left: 10px;">Alternative domain name system&sup1;</h3><br>
 
<hr>
 
<hr>
<html><img style="position: relative; zop: -50px;right: 100px;" align=right width=175 src=https://meansofproduction.biz/images/DNSnBINDimV6.png> </html>
+
<blockquote>
<blockquote><blockquote>
+
<html><img style="position: relative; top: 80px;right: 100px;" align=right width=160 src=/images/DNSnBINDimV6.png> </html>
Alt-rooted means that an autonomous name system distinct from just the priced IANA system is in use.<ref> see [[:en:Alt root|<span style="color: pink;">Alt root</span>]]</ref>
+
Alt-rooted means that an autonomous name system distinct from just the priced IANA system alone is in use.<ref> see [[:en:Alt root|<span style="color: pink;">Alt root</span>]]</ref>
 
+
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:
Beginning in 2019, a migration of virtually all content in my dev space, with the exception of a few necessary public pages, <br>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 it means a system of autonomous peers with allocation of the TLDs from a central authority here.  
 
 
 
A reasonable effort for a free service level is committed that just works by:
 
 
<blockquote>
 
<blockquote>
 
adding the following name servers, which are non-recursive, in desired order to your active resolver(s):
 
adding the following name servers, which are non-recursive, in desired order to your active resolver(s):
  
*ns0.meansofproduction.&lt;TLD&gt;
+
*ns0.&lt;IANA_TLD&gt;
*ns1.meansofproduction.&lt;TLD&gt;
+
* . . .
</blockquote>
+
*ns&lt;n&gt;.&lt;IANA_TLD&gt;
or their ip addresses if your resolver requires it. &lt;IANA_TLD&gt; is the IANA delegated Neustar .biz TLD thru March 2020, and the same named but alt-rooted here thereafter
+
 
with a variable point of contact between IANA namespace and the autonomous system.
+
where &lt;n&gt; is currently 1, or their ip addresses if your resolver requires it and where
 +
</blockquote><blockquote>
 +
&lt;IANA_TLD&gt; is the IANA delegated <ol><li>Neustar <b>meansofproduction.biz</b> thru May 2019</li><li>Donuts <b>sameboat.live</b> thru October 2021</li><li>A different and TBD later name thereafter</li></ol>
 
</blockquote>
 
</blockquote>
<blockquote>
+
Paid<span style="color: gold;">&sup2;</span><ref>Price for the full SaaS without any physical resources other than control and delivery bandwidth kept under  <html><a style="color: pink" title="Current fx" href=https://meansofproduction.biz/imu.php onclick="return popitup('https://meansofproduction.biz/imuq.php?qg=10')">10 &#24037;</a></html> per TLD quarter assuming only stablity of fiat basket basis of the &#24037;.</ref>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.
Paid <span style="color: gold;"> &sup2;</span><ref>Price for the full SaaS without any physical resources other than control and delivery bandwidth kept under  <html><a style="color: pink" title="Current fx" href=https://meansofproduction.biz/imu.php onclick="return popitup('https://meansofproduction.biz/imuq.php?qg=10')">10 &#24037;</a></html> per TLD quarter assuming only stablity of fiat basket basis of the &#24037;.</ref> users have access to recursion and additional services up to continuous live maintenance by intelligent agency. This is done in a framework of migration of one or many prexisting clean&sup3; or used linux instances into our dockerized OS abstraction "MCP". The abstraction implements a single system image with the referenced intelligent systems support for an overall Domain Control Program ("DCP").
 
<p>Users of the "sameboat/C-六" core PHP CMS have significant DNS functionality outside the DCP/MCP context, in ordinary clients and servers.</p>
 
</blockquote>
 
<blockquote>
 
  
</blockquote>
+
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:
As used here, the background operation of the public priced name systems are assumed as needed, excluded where prohibited, 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:
 
 
<ul>
 
<ul>
 
<li>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.</li>
 
<li>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.</li>
Line 41: Line 33:
 
<li>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.</li>
 
<li>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.</li>
 
</ul>
 
</ul>
 +
An equivalent function is assumed for peer operators, as provided by my <span class=plainlinks>[https://dnseppus.meansofproduction.biz/doc/about <span style="color: cyan;"> DNS/EPP tooling</span>]</span> merged with the <span class=plainlinks>[https://fred.nic.cz <span style="color: cyan;">FRED</span>]</span> 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.
 
</blockquote>
 
</blockquote>
 
<hr>
 
<hr>

Revision as of 17:41, 21 April 2019

Alternative domain name system¹



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 <n> is currently 1, or their ip addresses if your resolver requires it and where

<IANA_TLD> is the IANA delegated

  1. Neustar meansofproduction.biz thru May 2019
  2. Donuts sameboat.live thru October 2021
  3. A different and TBD later name thereafter

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 stablity 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.