DNS and Domain Requirements
Prepare public and administrative domain names without exposing production infrastructure in documentation.
Domain names are external configuration. The edition registry supplies safe placeholders; the operator supplies the actual public web, admin, and API URLs through the deployment configuration.
Boundary
The public web surface, administrative surface, and API must route to the matching application service. Domain configuration must not change edition identity, database namespace, or search namespace. Use example hostnames in planning material and keep real DNS values out of public documentation.
Verification
Confirm DNS records resolve to the intended edge, verify the reverse proxy routing, and test each application surface through its configured hostname. Passing DNS checks does not prove TLS or application readiness.