Alternative DNS root: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
Line 1: Line 1:
== Dominion Lede ==
== Dominion Lede ==


I maintain a ''private'' TLD domain system based on open source software that is freely available and which establishes an alternate domain name space. A "dominion" is really Just this plus all the software running under this ordinary Bind 9 namespace although there is quite a bit of it. In my system, each operating entity gets a complete name space into which the public internet maps as usual. The five ICANN domains constituting my dominion are unified in the ''dominion'' wik-cso.dom which is just the top level name I have reserved for myself in interfacing with the autonomous routing systems of others with whom I establish peer networking. The dominion system assumes a number of elements generally optional until now are uniformly enabled. In particular IPV6, Mutlicasting, and the maintenance of ones own TLD are assumed and each domain is assumed to be an agency for a set of identified persons. It is this latter TLD collaboration which constitutes the dominion system.
I have conceived and implement a ''private'' TLD domain system based on standard open source software which I call a ''dominion''. A "dominion" is really just the '''aii.biz''' scheme for peer-peer routing based on such software in an ordinary Bind 9 IP V6 namespace although there is quite a bit of it.  


Peers in the dominion agree on what portions, if any, of the system, they will route and can also use this filter the public internet.
In my construct, each peer operates a complete name space into which the public internet maps under their control. The five ICANN domains constituting my dominion are unified in the ''dominion'' wik-cso.dom which is just the top level name I have reserved for myself in interfacing with other autonomous peers. The dominion system assumes a number of elements generally optional until now are uniformly enabled. In particular IPV6, Mutlicasting, and the maintenance of ones own TLD are assumed and each domain is assumed to be an agency for a set of identified persons. It is this latter TLD collaboration which constitutes the dominion system. Names at the top level are claimed FCFS as peers join the network, with .dom reserved for my source network.
 
I assume that those using my software and peering with my DNS servers will delegate the TLD ".dom" to my servers and provide a similar TLD of their choosing or use their exiting ICANN domains routed by me to thru their dominions.


== English Lede ==
== English Lede ==