Difference between revisions of "Alt root"

From Cibernética Americana
(252 intermediate revisions by the same user not shown)
Line 1: Line 1:
Alt-rooted means that a name system other than that of the forces that be is in force see [[:en:Alt root]].
+
<html><script language="javascript" type="text/javascript">
As used here it means peering with the name servers here, which is automated like in letsencrypt as part of the SSO/user provisioning setup.
+
<!--
 +
function popitup(url) {
 +
newwindow=window.open(url,'name','height=600,width=450;');
 +
if (window.focus) {newwindow.focus()}
 +
return false;
 +
}
 +
</script></html>
 +
<div style="background-color: grey; color: white;">
 +
<div style="position: relative;left: 40px;text-align: left;width: 500px;">
 +
<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>
 +
<h5 style="text-align: center;">Domain Engineering TLD</h5>
 +
<h3 style="text-align: center;position: relative;top: 5px;left: 10px;">[[:de:Kastalien|<span
 +
    style="background-color: navy; color: silver;"> &nbsp; KASTALIEN &nbsp; </span>]] &nbsp;
 +
    <span style="font-size: 12px;background-color: gainsboro; "> [[:en:Rectification of names| &nbsp;alternative domain name system ]]</span>&sup1;</h3><br>
 +
</div>
 +
<blockquote>
 +
<html>
 +
<img style="position: relative; top: 115px;right: 95px;" align=right width=160 src=https://meansofproduction.biz/images/DNSnBINDimV6.png><br>
 +
<a title="Forked at github, under consideration" href=https://namecoin.org><img style="position: relative; top: 245px; left: 55px;" align=right width=50px align=right src=https://meansofproduction.biz/images/namecoin.png></a><a title="Under consideration" href=https://dnscrypt.info><img style="position: relative; top: 165px; left: 15px;" align=right width=50px align=right src=https://meansofproduction.biz/images/dnscrypt.cd47d19.png></a>
 +
</html><br>
 +
<span style="background-color: darkslategray;color: white;">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></span> 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:
 +
<blockquote>
 +
adding the following name servers, which are non-recursive, in desired order to your active resolver(s):
  
 +
*ns0.&lt;IANA_ZONSFX&gt;
 +
* . . .
 +
*ns&lt;n&gt;.&lt;ZONSFX&gt;
  
The easiest way to do this this is add the following servers, which are non-recursive, to the top of your resolver config such as resolv.conf:
+
where &laquo;IANA_ZONSFX&raquo; is the linking zone in the priced name system and, &lt;n&gt; is currently 1, or their ip addresses if your resolver requires it and
 +
</blockquote><blockquote style="color: yellow;font-weight: 600;">where the linking zone uses the designated
 +
&lt;IANA_ZONSFX&gt;
 +
<ol><li><strike>Neustar <b>meansofproduction.biz</b> thru May 2019</strike>*;</li>
 +
    <li>Donuts <b>sameboat.live</b> thru October 2021;</li>
 +
    <li> TBA </li>
 +
</ol>While there will always be a public linking zone, the intent is to self route all my domains over time, restricting the intersection to a single commercial zone.
 +
&#42; <span style="font-size: 10px;color: lime;font-weight: 900;background-color: darkslategray; ">may still be IANA/ICANN routed but not used as linking zone. thoughtcrime.dom and ai-integration.dom will replace the .biz suffix after March 2021.</span>
 +
</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 stability 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.
  
 
+
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:
*daclips.meansofproduction.biz
+
<ul>
*malta.meansofproduction.biz
+
<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>IPV6 and TLS are defaults, 4 and plain text special cases.</li>
or their ip addresses if your resolver requires that.
+
<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>
 +
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>
 +
<hr>
 +
<references/>
 +
<blockquote>
 +
&sup3; <font size=1>"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.</font>
 +
<html><a title="The Alt-Root I maintain" href=https://sameboat.live><img align=right src=https://meansofproduction.biz/images/kastalien.png></a></html>
 +
</blockquote>
 +
<br>
 +
</div>

Revision as of 10:35, 7 February 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_ZONSFX>
  • . . .
  • ns<n>.<ZONSFX>

where «IANA_ZONSFX» is the linking zone in the priced name system and, <n> is currently 1, or their ip addresses if your resolver requires it and

where the linking zone uses the designated

<IANA_ZONSFX>

  1. Neustar meansofproduction.biz thru May 2019*;
  2. Donuts sameboat.live thru October 2021;
  3. TBA

While there will always be a public linking zone, the intent is to self route all my domains over time, restricting the intersection to a single commercial zone.

* may still be IANA/ICANN routed but not used as linking zone. thoughtcrime.dom and ai-integration.dom will replace the .biz suffix after March 2021.

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.