Make an unexpected record change visible.
What it checks
DNS monitoring compares supported records with the configured expectation. A change is recorded as a change event; it should not automatically be described as downtime.
Set it up thoughtfully
Select the record type and expected value intentionally. An HTTP check and an independently scheduled DNS check use two monitor slots because they test different behavior.
Know the boundary
DNS caches, TTLs and resolver location affect observations. This is not a promise that every resolver worldwide has converged.