Infraova
Resources›Guides›How to review a proposed DNS change

Guide

How to review a proposed DNS change

Understand what Infraova has proposed, why it was proposed, and what to check before approving.

AgencyEnterprise·5 min read

The situation

When Infraova detects an issue that can be resolved by a DNS change, it prepares a specific remediation proposal. Your team reviews it before any change is made.

Before you begin

A remediation proposal waiting for review in Infraova
Understanding of the issue that triggered the proposal
Authority to approve or decline DNS changes for the affected domain

For agencies: For client domains, confirm the client is aware of the proposed change where appropriate. Policy changes like DMARC enforcement may have client communication implications.

The operational path

01Receive proposal
02Understand the issue
03Review the change
04Assess impact
05Approve or decline

The goal isn't just to find the error. The goal is to move from detection to a verified infrastructure state.

What could have caused this?

Cause

What changed

Possible impact

Detected failure

Infraova found an issue requiring a fix

Proposal generated automatically

Step by step

01Understand the issue behind the proposal

Every proposal is connected to a detected issue. Start by understanding what Infraova found.

What to check

✓Read the issue description in the proposal
✓Review the severity and the impact on the domain
✓Check when the issue was first detected
✓Confirm you understand why the change is being proposed
02Review the proposed record

The proposal includes the exact DNS record value that will be set if you approve.

What to check

✓Check the record type (TXT, MX, CNAME, A, etc.)
✓Read the proposed value and confirm it is correct
✓Confirm the current (before) value and the proposed (after) value
✓Check whether any existing configuration will be removed or replaced

With Infraova

Infraova shows the exact record value, not a generic suggestion. Review it as you would any production DNS change.

03Assess the impact

Consider the downstream effects of the change before approving.

What to check

✓Will the change affect email sending for the domain?
✓Will it affect any services relying on the current record value?
✓Is the timing appropriate?
✓Is there anything the proposal might not account for?
04Approve or decline

If the proposal is correct and the impact is acceptable, approve it.

What to check

✓If approving: confirm the decision — the change executes immediately
✓If declining: add a note explaining why so the proposal can be revised
✓If unsure: gather more information before deciding

Expected result: If approved, the change executes and Infraova begins verification. If declined, the issue remains open.

You decide. Infraova executes.

Infraova can propose and execute an approved infrastructure change, but it does not independently decide to modify client infrastructure. Every proposed change requires explicit authorization before execution.

Infraova detects
↓Infraova diagnoses
↓Infraova proposes
↓YOU APPROVE
↓Infraova executes
↓Infraova verifies

Key takeaway

Every proposal is the result of Infraova's analysis — but your review authorizes it. Read the issue, understand the proposed change, assess the impact, and decide with confidence.

Turn this playbook into a continuous workflow

Without Infraova

Someone discovers the issue
↓Someone investigates manually
↓Someone decides what to do
↓Someone makes the change
↓Someone checks whether it worked

With Infraova

Monitor
↓Detect
↓Prioritize
↓Propose
↓Approve
↓Remediate
↓Verify
↓Record

The guide teaches you how to solve the problem once. Infraova keeps watching for it after you're done.

Want the product-level details?

Guides answer "How do I solve this?" Documentation answers "How does Infraova work?"

Stop discovering infrastructure problems manually.

Infraova continuously monitors your client and business infrastructure, identifies meaningful problems, proposes the next action, executes approved changes, and verifies the result.