Domain Engineering TLD
Domain space domains are subject to being alt-routed, either same named, ICANN suffix either replaced by .dom, or just dropped. As used here. alt root 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):
- . . .
where «IANA_ZONE», the linking zone or TLD in the priced name system and, <n> is currently 2, or their ip addresses if your resolver requires it and
where the zone rotation assignments are
- thru 2023-09 <DS_ZONE> ::= 'meansofproduction' , <IANA_ZONE> ::= 'biz' (Neustar)
- — TBA Early 2023
... for ai-integration [.dom]:
- 2005-03 - 2025-02 <DS_ZONE> ::= 'ai-integration' , <IANA_ZONE> ::= 'biz'
- Early 2022 — mecha.dom . aii.biz and aii.dom will diverge from this point and aii.biz will not have public routing by 2025.
... for sameboat [.dom]:
- thru 2022-09 <IANA_ZONE> ::= 'live' (Donuts)
- 2022-10 — <IANA_ZONE> ::= TBA Early 2022
The rotating linking zone is the distinguising feature of my alt root concept which otherwise is ordinary DNS/EPP.
A compromise between stability and flexibility/independence from the priced system is struck by 3 year rotation of a IANA TLD and 90 days of dual routing of the old and new during the rotation.
The canonical mapping from state actor name spaces such as IANA into .dom is to simply drop the linking zone and replace it by the one its owner designates for use in domain space.
Names wholly within the alt system lack the linking suffix (or equvalently use .dom) and are thus not affected by linking suffix rotation.
Operators manage impact if any in their domain spaces across linking zone rotations, including determining their own epoch duration policies, above are for core domain space.
* An example is thoughtcrime.biz, thoughtcrime.dom is already the reference domain but tcb.biz will route publicly for a while and then only via my root for the .biz suffix.
Paid²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.
- Simple name seeking registrars are prohibited. Registrars must offer the name service free bundled with value added services.
- 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 mymerged with the 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.