Infraova
Resources›Guides›How to verify a DNS change

Guide

How to verify a DNS change

Confirm that a DNS change is live in the infrastructure and matches the expected state.

BusinessAgency·4 min read

The situation

A DNS change is not complete when it is submitted. It is complete when the live infrastructure reflects the expected state. Verification is the step that confirms the change worked as intended.

Before you begin

A recently executed DNS change
Knowledge of what the expected record value should be
Access to Infraova for automated verification

The operational path

01Execute change
02Wait for propagation
03Check live state
04Confirm result
05Record

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

Change submitted

DNS record updated at provider

Propagation required before live

Step by step

01Allow for DNS propagation

DNS changes do not take effect instantly. Propagation time depends on the record's TTL.

What to check

✓Check the TTL of the changed record
✓For low TTL records (60-300 seconds): verification can begin quickly
✓For higher TTL records: allow more time before checking
02Verify through Infraova

Infraova verifies executed remediations automatically.

What to check

✓Check the verification status in the remediation record
✓Confirm the live value matches the approved proposal value
✓Confirm no related records were unintentionally affected

Expected result: Verification passes — the change is live and correct.

With Infraova

Infraova performs automated verification immediately after execution — querying the live DNS state and confirming it matches the approved change. If verification fails, the issue stays open.

03Confirm the functional result

Beyond the DNS record value, confirm the intended outcome is working as expected.

What to check

✓For SPF changes: check authentication results in a recent message header
✓For DKIM changes: confirm signatures are passing for outgoing messages
✓For MX changes: confirm mail routing is functioning correctly

Expected result: The change is verified at both the DNS record level and the functional level.

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

A submitted change and a working change are not the same thing. Confirm the live state before considering an issue resolved.

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.

Start monitoring →Learn how Infraova works →

Continue the playbook

How to approve an infrastructure change

Read guide →

How to handle failed remediation

Read guide →

Want the product-level details?

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

Verification →

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.

Start monitoring →Explore Infraova →