Aux root
What is DNS?
above is important
Domain space (DS) is just the regular public internet with an added top level domain .dom and its support which operators use for greater control of their name spaces, as a peerage of autonomous operators routing names upon their discretion. The default in core domain space is all ICANN/IANA TLDs plus one but other operators may choose something else. Since the public roots are generally not affected, we use the term "Aux(lliary) root" instead of Alt-root.
User name services are provided thru the .dom content mgt system (DCMS).
KASTALIEN is also the marque for the single authentication realm (SAR).
.
Go There
.dom
Domain Engineering TLD
KASTALIEN peer-peer name system ¹
These have been private or unused since their public epoch.
Epoch Vendor <NAME> <ZONE> 'kybernet' 'com' before 2000 Verisign 'commoditysoftware' 'org' before 2014 Verisign 'thoughtcrime' 'biz' before 2023 Neustar 'greentravel' 'app' before 4/2025 Dont Care
Add 1 or more of these name servers ( or their addresses ) to use our aux root:
- ns.<LINKING_ZONE>
- . . .
- ns<n-1>.<LINKING_ZONE>
where<LINKING_ZONE> ::= <DS_ZONE>.<IANA_ZONE>
A linking zone is a bridge from the public name system, n in <n-1> is currently 2 and
the zone rotations are
<LINKING_ZONE> Epoch Vendor <DS_ZONE> <IANA_ZONE> 'sameboat' 'network' 2022-05 — 2027 Donuts 'ai-integration' 'biz' 2005-03 — 2025-02 Neustar As of 25 Jan 2025 all IANA names via Square Space
Unclear/uninterested about their registry status, upstream authority if any.'meansofproduction' 'biz' 2006-11 — 2024-10 Neustar 'meansofproduction' nil (root) 2025-01-25 core DS aii.biz goes mostly private N/A 2025-01-01 DS 'sameboat' 'live' 2017-11 — 2022-11 Donuts <apex>* 'live' 2022-08 — DS
- *Suffixes dropped in the wild are generally still routed in domain space.
* An example is thoughtcrime.biz, tcb.biz will route publicly thru March 2023 and then only via DS.
The rotating linking zone prevents any lock-in in the interface to the priced name system.
A compromise between stability and flexibility/independence from the priced system is struck by rotation of a IANA TLD and a period of dual routing of the old and new during the rotation. Canonical mappings from public (IANA) name space into a private domain space are to simply drop the IANA TLD, replace it by .dom for core DS or other Operators designated suffix (which can be nil to replace a whole TLD).
Names only routed in a domain space lack an IANA suffix (or equvalently use .dom) and are not affected by linking zone rotation.
Operators manage impact if any in their domain spaces across linking zone rotations, including determining their own epoch duration policies, those listed here are for core domain space.Entitled 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:
- IPV6 and TLS are defaults, 4 and plain text special cases.
- Operators of domain spaces determine which TLDs they recognize. Core domain space allocates its TLDs FCFS to AKPERSONs, other operators may have different policies. For simple interop Operators use a single reserved name: ".dom" for their private/peer namespace.
- Simple name rent seeking registrars are obviated in core DS as DCP there runs a unified registry/registrar but downstream Operators may instantiate multiple registrars, a single registrar isnt a system limitation but we dont support the billing components of FRED only the multiple registrars.
Each domain space is served by an instance of the FRED NIC software adapted for control by DCP.
