How It Works

Under the hood

OneDollarDNS continuously polls your domain's DNS records and compares each snapshot to the previous one. Here's exactly how that works.

Domain discovery

When you add a new domain, OneDollarDNS kicks off an automated discovery phase. Rather than asking you to manually list every hostname, the system probes a curated list of common subdomains and dynamically expands based on what it finds.

The discovery process checks the following:

  • Common hostnames: @ (apex), www, mail, api, app, admin, blog, cdn, staging, dev, and more
  • Email authentication records: _dmarc and the DKIM key names used by common providers, including Google Workspace, Microsoft 365, Mailchimp, SendGrid, Fastmail, Proton, and Zoho
  • MX record targets (mail servers often have their own DNS records)
  • NS record targets (authoritative nameservers)
  • CNAME targets that point back to the same domain (followed recursively)

Only hostnames that return at least one DNS record are saved as monitored hosts. The domain view shows a discovering indicator while this process runs. Once complete, monitoring begins immediately.

Continuous monitoring

After discovery, each domain is checked on a recurring schedule. By default, every host on a domain is checked every hour. The Frequent Monitoring add-on lets you mark individual hosts as Priority Hosts, which are checked every 5 minutes. The domain's other hosts stay on the hourly schedule.

Every monitoring run queries the domain's authoritative nameservers directly, bypassing caching resolvers, so you see the current state of your DNS records as they exist at the source rather than a cached copy.

If one of a domain's nameservers is briefly unreachable, we try another before treating it as a problem. If no nameserver gives a usable answer during a check, we skip that check instead of reporting your records as removed, and check again about 5 minutes later. If it's still failing, you get one alert:

  • Nameservers not responding when every nameserver stops replying. One message lists every domain of yours on those nameservers, plus any monitored host in a subdomain delegated to them, instead of one alert per domain.
  • DNS isn't answering when the nameservers reply, but not with usable answers for that domain. This usually means your DNS provider is no longer serving the domain.

You get a second message once DNS answers again. Because a domain's nameservers can briefly disagree while a change is propagating, you may occasionally see a change alert followed shortly by another as things settle.

Supported record types

OneDollarDNS monitors all of the following DNS record types for every host:

Type Description
A IPv4 address mapping
AAAA IPv6 address mapping
CNAME Canonical name / alias target
MX Mail exchange server with priority
NS Authoritative nameserver
TXT Arbitrary text (SPF, DKIM, verification tokens, etc.)
CAA Certificate Authority Authorization
SRV Service locator (hostname, port, priority, weight)

Snapshot comparison

Each DNS lookup is compared against the host's current snapshot: a record of every value and TTL its nameservers returned. A new snapshot is saved only when something differs, so a host whose records stay the same keeps the snapshot from its last change.

Four types of changes are detected:

Added

A record exists in the new snapshot but not in the previous one. For example, a new A record pointing to a second IP address.

Removed

A record existed previously but is no longer present. For example, an MX record being removed.

Modified

A record of the same type was present before and after, but its value changed. For example, a TXT record with an updated SPF policy.

TTL changed

A record set kept its values, but its TTL changed. For example, an A record's TTL lowered from 3600 to 300 seconds ahead of a migration. If a set's records have different TTLs, the lowest counts, since that's how long resolvers cache the set. Two separate checks have to see the new TTL before it's recorded, so nameservers that briefly disagree, or that count a TTL down from a cache, don't cause alerts.

Each detected change produces a DNS alert that appears on the dashboard and the DNS Changes page and sends a notification. Changes to a record type you've muted on a host, and CDN address rotations when Ignore CDN IP rotations is on, are recorded without a notification and don't need review.

Manual check

You can trigger an immediate check at any time from the domain detail page by clicking Check now. This queues a DNS lookup for all hosts in the domain regardless of whether a host is marked as Priority. Useful right after making intentional DNS changes to confirm they've propagated correctly.

Custom hosts

If a host wasn't found during automated discovery, you can add it manually. Custom hosts are monitored on the same schedule as auto-discovered ones. If a manual host returns no DNS records at all, it remains in the list but shows as No records until records are found.

You can also remove any host (auto-discovered or manual) at any time from the domain page.

Zone file import

If you already have a BIND-format zone file for your domain, you can use it to populate your monitored host list in bulk instead of adding hosts one at a time. Zone file import is available in two places:

  • During domain creation — attach a zone file in the Add domain dialog. Hosts are imported immediately after the domain is created.
  • From the domain detail page — click Upload zone file next to the Add host button at any time.

The parser understands standard BIND zone file syntax, including:

  • $ORIGIN and $TTL directives
  • Multi-line records using parentheses
  • Relative and absolute (FQDN) owner names
  • Whitespace-inherited owner names (continuation lines)

SOA records and wildcard entries (*) are skipped automatically, as are any out-of-zone names that don't belong to the domain being imported. Hosts that already exist are not duplicated. If a host was previously auto-discovered, importing it via zone file removes the auto-discovered label and treats it as an explicit host going forward.

Each imported label is queued for DNS resolution in the background. The zone file must be no larger than 512 KB.

Related