These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- DNS & Domain Management
- Data model and import order
The tables behind DNS & Domain Management
DNS & Domain Management ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 12
- Features
- 7, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Domain portfolio:
Domains holds the owned name, registrar, expiration, renewal choice and Owner reference to People.
DNS work:
DNS records links each entry to Domains and carries record type, host, value, TTL and status.
Service context:
Services links to Assets, Changes, Incidents, Problems and service requests.
Response chronology:
Incident updates links to Incidents and its People author.
External messages:
Integration receipts holds provider, external event ID, receipt time, payload hash and status.
People and access:
People references Users and supplies ownership and assignment across the model.
Every table, by feature
- Domains1
- DNS Records2
- Changes2
- Incidents4
- Service Requests3
- Services and Assets3
- Integration Receipts1
- Shared and settings1
- Domains
A record is one owned domain; the team uses this to track registration, renewal, and ownership.
Linked to People
- DNS records
A record is one DNS entry for a domain; the team uses this to manage and audit routing and mail settings.
Linked to Domains - Domains
A record is one owned domain; the team uses this to track registration, renewal, and ownership.
Linked to People
- Changes
A record is one planned change to a service; the team uses this to schedule, assess risk, and track rollout.
Linked to Services - Services
A record is one service the team provides; the team uses this to track its importance and health.
Linked to People
- Incidents
A record is one service disruption; the team uses this to track response, resolution, and impact.
Linked to Services, Assets, People - Incident updates
A record is one status note on an incident; the team uses this to keep everyone informed as it progresses.
Linked to Incidents, People - Services
A record is one service the team provides; the team uses this to track its importance and health.
Linked to People - Assets
A record is one piece of tracked equipment; the team uses this to know where it is and what it supports.
Linked to Services
- Service requests
A record is one request from a team member; the team uses this to track fulfillment against deadlines.
Linked to People, Services - Services
A record is one service the team provides; the team uses this to track its importance and health.
Linked to People - People
A record is one team member; the team uses this to know their role and link them to their work.
Linked to Users
- Services
A record is one service the team provides; the team uses this to track its importance and health.
Linked to People - Assets
A record is one piece of tracked equipment; the team uses this to know where it is and what it supports.
Linked to Services - Problems
A record is one underlying issue behind incidents; the team uses this to track root causes until they're resolved.
Linked to Services, People
- Integration receipts
A record is one inbound message from an outside system; the team uses this to confirm and trace integration activity.
Keys and references
Keep stable IDs for domains and linked records. Match DNS records.Domain to the intended Domains entry, and keep Domains.Owner attached to the accountable person. A provider event ID belongs to the inbound receipt. The receipt has no DNS entry reference; match it to the publication work before changing the DNS status. Users and People are separate records linked by People.User.
Migration order
- Load Users and People, then agree active owners and reviewers.
- Load Services and Assets for the operational context.
- Load Domains with registrar, expiration, renewal choice and owner.
- Load DNS records against the correct Domains entries.
- Load open Changes, Incidents, incident updates, Problems and service requests.
- Reconcile integration receipts and current statuses with provider evidence.
Set up DNS & Domain Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.