dnswatchdog.iodocs

Scan History

View every scan conducted across your DNS infrastructure with change summaries and timing.

Open Scan History →

The Scan History page shows every scan that has been conducted across your DNS infrastructure. Each scan is recorded with its type, target, duration, change summary, and who initiated it.

The Scan History page showing a list of scans with type badges, change summaries, and duration

Scan types

DNS Watchdog runs three types of scans:

Scan TypeTriggerTarget
Initial SyncRuns automatically when you first connect a providerSingle provider — discovers all zones and records
Daily ScanAutomated, runs every day at 02:00 UTCAll providers — checks for changes across your entire DNS estate
Provider ResyncManually triggered by a userSingle provider — re-syncs all zones and records

Each scan type is shown with a colour-coded badge for quick identification.

What's shown

For each scan, the table displays:

ColumnDescription
Scan TypeColour-coded badge (Initial Sync, Daily Scan, Provider Resync)
ProviderTarget provider name, or "All Providers" for daily scans
ChangesSummary badges showing records added (+), changed (~), and removed (-)
StartedStart time and relative age (e.g. "2 hours ago")
DurationHow long the scan took to complete
Initiated By"Scheduler" for automated scans, or the user's email for manual resyncs

Summary cards

Summary cards at the top of the page show:

  • Running — number of scans currently in progress
  • Total — total number of scans recorded

Filtering

You can filter scans by status:

  • In Progress — scans that are currently running
  • Completed — scans that have finished

The page auto-refreshes every 15 seconds so you can monitor running scans without manually reloading.

Viewing scan results

Each scan row includes a View results link that takes you directly to the Change Log filtered to that specific scan. This lets you see exactly what changed during that scan — which records were added, modified, or removed, and which issues were detected or resolved.

This deep linking makes it easy to investigate what happened during a particular scan without manually setting up filters.

On this page