DNS: Difference between revisions

(100 intermediate revisions by the same user not shown)

Line 1:

__NOTOC__

<tr><td> [[:en:DNS]] </td><td>Go here for an overview of what DNS is </td></tr>

<div style="height:50px;background-color:yellow;color:red;font-size:14px;"><br>  <b> Here is the big and simple Truth you must first understand about internet domain names — </b>  </div>

<tr><td> [https://dnseppus.meansofproduction.biz dnsepp upgrade service]</td><td> A support site for my first paid DNS work] </td></tr>

Registries and Registrars don't own names, they just provide services to the natural owners, those that create them, in the priced name system with a suffix for which there are authoritative registries. Once you own a name it can never be taken from you as long as you are routing it, albeit with a fee to a registrar in the public system which is constructed to prevent that, as a vital principle. Suffixes are no exception, nobody really owns them although one or another registry may be the authoritative top level name controller at a given time. The suffixes were originally considered to be public, i.e. socially owned domains or unowned generic types (.com, .edu, .gov, .org, etc.).

</blockquote>

<tr><td align=right> [[:en:DNS]] </td><td>Go here for an overview of what DNS is .</td></tr>

<tr><td align=right> [[Aux root]]</td><td> About our namespace variant. </td></tr>

<tr><td align=right> [https://devops1.sameboat.network/AboutDNS SB DevOps DNS]</td><td> About DNS in the Sameboat C-六 network . </td></tr>

<tr><td align=right> [https://dnseppus.meansofproduction.biz/doc/about dnsepp upgrade service]</td><td> A support site for my first paid DNS work .</td></tr>

</table>

</center>

Since there is substantial resistance to the notion of you owning your namespace, it's important to clarify that while I am selling a particular software and service solution, it is based entirely, at the level of interface with the existing inet, on existing and proven softwares with the central distinction being delimitation of the decision to privatize public name space by providing a superspace that is private in the other sense, restoring the public service nature implicit in the original scheme but also fulfilling the autonomy only ever implicit before now, originally ARPA had complete authority which ultimately devolved to the capitalized registries. Because of essentially being, at the level of the name system, just an application/configuration of otherwise unchanged system software, the Exe Novel can present a new view of name space smoothly, if you permit it.</blockquote>

<blockquote style="font-size:16px;text-align:justify;">AKPERSONs are entitled to this service as per their capitation class as detailed in the About DNS text in the SB C-六 network link above. Third class human users are only potential AKPERSONs so they see domain space from the wild and generally lack private namespace access.

I am simply fulfilling the original principles, creating group centric namespaces and enabling the creation of suffixes also known as Top Level Domains. Generic domain space as implemented by me extends and is based on the priced singly rooted name system and is meant to augment not replace it. Think of the public system as root domain space, the common core of all domain spaces, and of using .dom as giving you the possibility of selecting which groups control your namespace or doing it yourself.<br><br>

</blockquote>

<html><a style="position:relative;top:0px;font-size:20px;color:cyan;" href="https://meansofproduction.biz/pub/SpanishCastleMagic.mp4">No It's Not in Spain, but it's a groovy name just the same.</a></html>

</center><br>

</blockquote>

</div></div>

Navigation menu

Page actions

Page actions

Personal tools

About

Search

forewords

novel

Tools

@@ Line 1: / Line 1: @@
 <div class="plainlinks" style="background-color: white; color: black;">
 __NOTOC__
-<div style="background-color: white;color: black;"><blockquote><br>
+<div style="background-color: black;color: white;"><blockquote><br><br>
 <center>
-<table width=50%>
+<blockquote>
-  <tr><td> [[:en:DNS]] </td><td>Go here for an overview of what DNS is </td></tr>
+<div style="height:50px;background-color:yellow;color:red;font-size:14px;"><br>&nbsp; <b> Here is the big and simple Truth you must first understand about internet domain names &mdash; </b>&nbsp; </div>
-  <tr><td> [https://dnseppus.meansofproduction.biz dnsepp upgrade service]</td><td> A support site for my first paid DNS work] </td></tr>
+<blockquote style="font-size:20px;text-align:justify;">
+Registries and Registrars don't own names, they just provide services to the natural owners, those that create them, in the priced name system with a suffix for which there are authoritative registries. Once you own a name it can never be taken from you as long as you are routing it, albeit with a fee to a registrar in the public system which is constructed to prevent that, as a vital principle. Suffixes are no exception, nobody really owns them although one or another registry may be the authoritative top level name controller at a given time. The suffixes were originally considered to be public, i.e. socially owned domains or unowned generic types (.com, .edu, .gov, .org, etc.).
+</blockquote>
+</blockquote>
+<table style="background-color: aliceblue; color: navy;font-weight:700;" width=50%>
+  <tr><td align=right> [[:en:DNS]] </td><td>Go here for an overview of what DNS is .</td></tr>
+ <tr><td align=right> [[Aux root]]</td><td> About our namespace variant. </td></tr>
+ <tr><td align=right> [https://devops1.sameboat.network/AboutDNS SB DevOps DNS]</td><td> About DNS in the Sameboat C-六  network . </td></tr>
+  <tr><td align=right> [https://dnseppus.meansofproduction.biz/doc/about dnsepp upgrade service]</td><td> A support site for my first paid DNS work .</td></tr>
 </table>
-</center>
+<blockquote>
+<blockquote style="font-size:20px;text-align:justify;">
+Since there is substantial resistance to the notion of you owning your namespace, it's  important to clarify that while I am selling a particular software and service solution, it is based entirely, at the level of interface with the existing inet, on existing and proven softwares with the central distinction being delimitation of the decision to privatize public name space by providing a superspace that is private in the other sense, restoring the public service nature implicit in the original scheme but also fulfilling the autonomy only ever implicit before now, originally ARPA had complete authority which ultimately devolved to the capitalized registries. Because of essentially being, at the level of the name system, just an application/configuration of otherwise unchanged system software, the Exe Novel can present a new view of name space smoothly, if you permit it.</blockquote>
+<blockquote style="font-size:16px;text-align:justify;">AKPERSONs are entitled to this service as per their capitation class as detailed in the About DNS text in the SB C-六  network link above. Third class human users are only potential AKPERSONs so they see  domain space from the wild and generally lack private namespace access.
+I am simply fulfilling the original principles, creating group centric namespaces and enabling the creation of suffixes also known as Top Level Domains. Generic domain space as implemented by me extends and is based on the priced singly rooted name system and is meant to augment not replace it. Think of the public system as root domain space, the common core of all domain spaces, and of using .dom as giving you the possibility of selecting which groups control your namespace or doing it yourself.<br><br>
+</blockquote>
+</blockquote>
+<html><a style="position:relative;top:0px;font-size:20px;color:cyan;" href="https://meansofproduction.biz/pub/SpanishCastleMagic.mp4">No It's Not in Spain, but it's a groovy name just the same.</a></html>
+</center><br>
+<html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=DNS></html>
 </blockquote>
 </div></div>