Registry
Copy model-free DNS presentation components from the DomainKit registry and compose them with your own data, transport, and product state.
The DomainKit registry contains small, source-distributed React components for DNS interfaces. Add the files to your application with the shadcn CLI, then own their markup, styling, and behavior.
These components are intentionally model-free. They accept plain props and do not import
domainkit, Effect, Atom, transports, provider clients, or persistence. Use the packaged
@domainkit/react flows when you need connection, planning, authorization, apply, verification, or
receipt-bound cleanup.
The registry follows shadcn conventions: your project needs an initialized components.json, each
item is installed into the configured ui alias, and required shadcn primitives are declared as
registryDependencies. The CLI installs those primitives automatically. Components accept native
element props and className, use data-slot attributes, and inherit the standard shadcn color,
radius, and focus-ring tokens from your application.
Registry items
DNS table
Render DNS records in a compact, responsive table.
DNS operation
Show one planned create, no-op, or conflict operation.
DNS status
Style a visible status label with an explicit tone.
Provider mark
Give a provider logo or mark an accessible visual wrapper.
Copy value
Add a copy action to a DNS value without a DomainKit dependency.
Async state
Present loading, empty, and error states with simple children.
Install from the registry
Install one item or several items directly into your application:
npx shadcn@latest add https://domain-kit.dev/r/dns-table.json https://domain-kit.dev/r/dns-operation.jsonpnpm dlx shadcn@latest add https://domain-kit.dev/r/dns-table.json https://domain-kit.dev/r/dns-operation.jsonyarn dlx shadcn@latest add https://domain-kit.dev/r/dns-table.json https://domain-kit.dev/r/dns-operation.jsonbunx shadcn@latest add https://domain-kit.dev/r/dns-table.json https://domain-kit.dev/r/dns-operation.jsonThe source is the contract. After copying an item, change its classes, icons, and composition to fit your design system. Keep host-owned credential custody, authenticated routes, persistence, and readiness policy outside these presentation components.