Sign in
PLATFORM / DOMAINS & DNS

Every address.
Connected to its service.

Keep your domain with your registrar. The planned DNS workflow connects delegation, application routing, and HTTPS without losing sight of what points where.

Explore the workflowFull product tour
Automation planned
Domain routing workspaceProduct concept
DOCKOCK / DOMAINSdockock.example
Explore domains & dns capabilities
Your main websiteConnect the root hostname to the public application.
Hostname
dockock.example
Target
Web application
Verification
DNS · route · HTTPS
A dedicated API addressRoute a subdomain to the matching application service.
Hostname
api.dockock.example
Target
Backend API
Verification
DNS · route · HTTPS
Records with a purposeConnect mail records to a separately configured mail system.
Records
MX · SPF · DKIM · DMARC
Target
Your mail system
Requirement
Mail runtime & operational checks
Automation planned
THE WORKFLOW

A clear path.
At every stage.

Follow the intended workflow, with availability explained above.

01

Review your domain

Inventory existing records before changing nameservers at your registrar.

02

Delegate and verify

Use the nameservers assigned during setup and wait for delegation checks.

03

Connect the service

Review records, map the hostname, and verify routing and HTTPS.

DESIGNED AROUND THE DETAILS

The context behind the controls.

Explore the decisions, operating responsibilities, and current implementation behind this part of DOCKOCK.

Explore the guides

Keep the domain you already own.

Your domain stays with your registrar. The planned flow asks you to delegate DNS using the nameservers assigned during DOCKOCK setup. Existing records must be reviewed before delegation so websites and email keep their intended routes.

Make configuration part of the deployment.

After delegation is verified, the intended workflow configures the records required by your application, maps the hostname to the selected service, and verifies HTTPS. DNS propagation and failed checks remain visible; a requested change is not treated as a verified result.

Connect web, API, and email records.

Use the same domain context for websites, application subdomains, and the records required by private email. The mail system needs its own capacity and lifecycle management; web routing alone does not create a working mail service.

Know what is being built.

DOCKOCK authoritative DNS is not currently implemented. Existing domain and edge foundations are partial. Dedicated DNS infrastructure, delegation verification, safe migration, and lifecycle operations must be completed before the automated experience is offered.

KEEP EXPLORING

Connect the next layer.

EXPLORE THE PLATFORMDeploymentsEXPLORE THE PLATFORMPrivate email
YOUR NEXT STEP

See the whole workflow.
Know where to begin.

Follow the product journey from your first VPS to connected services.

Take the product tourView access details