Features
Everything you need to run DNS for a subdomain
OrbiDNS pairs a strict, server-enforced namespace model with the record types and automation real projects need.
Multiple root domains
Claim names across every root domain the platform operates, each with its own rules.
Seven record types
A, AAAA, CNAME, TXT, MX, SRV and CAA with per-type validation before anything reaches DNS.
Namespace isolation
Every write is checked server-side against your hostname. Nobody can touch the parent zone or a neighbour.
Confirmed changes
Records show pending until the DNS provider confirms. Failures retry with backoff and surface clearly.
Scoped API keys
Per-key permissions, expiry and usage. Keys are hashed at rest and shown exactly once.
Audit trail
Every change is recorded with actor, request ID and before/after values.
Isolation
How namespaces are protected
When you claim john.orbinex.in, that hostname and everything below it — www.john.orbinex.in, _acme-challenge.john.orbinex.in — becomes your namespace.
Names are written relative to it: @ is the hostname itself, www is a child. Anything outside your namespace is rejected by the server, not just hidden in the UI.
Depending on the root domain, your records live in a shared, strictly bounded zone or in a dedicated zone delegated to you with NS records. Either way, provider credentials never leave the platform.
| Type | Name | Content |
|---|---|---|
| A | @ | 1.2.3.4 |
| CNAME | www | app.vercel-dns.com |
| MX | @ | 10 mail.example.com |
| TXT | _dmarc | v=DMARC1; p=none |
API
Built for automation
- Versioned REST API under /api/v1 with OpenAPI docs
- Bearer API keys with per-key scopes and expiry
- Async writes: 202 Accepted, poll until active
- Consistent error envelope with request IDs
curl -X POST "https://orbidns.example/api/v1/subdomains/{id}/records" \
-H "Authorization: Bearer $ORBIDNS_KEY" \
-H "Content-Type: application/json" \
-d '{"type":"A","name":"@","content":"1.2.3.4","ttl":300}'