1. DNS & Domain Management
  2. Frequently asked questions
FAQ

Questions, answered

Answers for teams preparing domain and DNS operations.

DNS & Domain Management

10 questions

Can't find it? Write to support@erp.ai.

How do I get started?

Click Get started, then use Proto to configure DNS & Domain Management for your business. Pilot a small owned-domain portfolio, one proposed DNS entry and a provider acknowledgment before expanding.

What belongs in a domain record?

Keep the domain name, registrar, expiration date, renewal choice and owner together so the next portfolio decision has context.

How are DNS entries reviewed?

A proposed entry links to its domain and carries type, host, value and TTL. The DNS Reviewer checks these details before approval.

When is an entry Published?

The team requests publication after approval. The entry is marked Published after the provider acknowledgment is reconciled.

Can the team see renewal work?

The portfolio includes expiration dates, registrar details, renewal choice and owner so upcoming decisions can be reviewed.

How do service changes fit?

A change links to a service and records risk, its scheduled start and end, a rollback plan and status for review.

Can we follow incidents?

Incidents carry priority, service, asset, assignee and response times. Authored updates keep the investigation chronology.

What happens to provider messages?

Integration receipts retain provider, external event ID, receipt time, payload hash and processing status for reconciliation.

What should we import first?

Start with people and services, then domains and linked DNS entries. Reconcile current entries with provider state before opening more work.

What drives cost?

See the pricing page for platform usage and implementation scope. Estimate imports and provider activity from the operating cycle you intend to run.

Set up DNS & Domain Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started