Domain Studio
Design domain records before changing a live network.
Owner-controlled browser application • access by arrangement
What you can accomplish
Prepare a reviewable domain-record plan before anyone changes DNS.
What you bring
A domain and a JSON record list. Each record needs type, name, value and a non-negative integer TTL. The authored Studio accepts A, AAAA, CNAME, TXT, MX and NS record shapes; shape validation is not full DNS validation.
Work through the task
- Start with a test domain such as example.invalid and a TXT record: name @, value local-draft, TTL 3600.
- In an approved Studio, validate and save the plan. Resolve local records to inspect the submitted list, then load the saved plan and compare it.
- Export the domain plan as JSON. Review the intended registrar, DNS authority and change approval separately before a live change.
What you leave with
A domain-plan JSON file with the domain, records and owner-local draft scope. The local resolver returns the proposed records; it does not query or publish authoritative DNS.
Where your work stays
Save writes the plan to the Studio’s browser-local VFS and compares readback. Export keeps a separate JSON copy. Clearing the browser or moving devices can lose the local copy.
If something fails
Malformed JSON, an invalid record shape or a missing saved plan stops that operation. A save/readback mismatch means retention has not been established. Correct the input or restore the exported copy; do not treat a local record as a registered domain.
Available access
The Studio is qualified for owner-controlled browser use. Public customers can prepare a scope here and request access; this page cannot register a domain, publish DNS or issue TLS.
Technical background, package access and updates
Purpose
Domain records enter a local validation and resolution workflow and are retained in the browser-hosted virtual filesystem. The purpose is to inspect proposed authority and naming relationships before deployment.
Working path
Records → validation → local resolution → retained draft.
Source identity
Domain-authority console, authority resolver and spatial compiler lineage. This Studio is a new derivative, not a renamed historical application. The original components retain their identities.
Availability and authority
Domain namespace routing selects a website path, including an unknown-path fallback. DNS authority controls delegation and name records. Execution binding identifies the host that performs an operation. These are separate boundaries: an HTTP catch-all is not DNS sovereignty. Live DNS, registrar writes, delegation and TLS verification are not bound. A saved record is a local draft, not a registered domain.
The four Studios have been installed, launched and reloaded in the owner-controlled AetherOS browser host. That qualification does not establish public access or cross-device state. Customer sign-in does not grant installation or administration rights.