Add-ons

Power up your monitoring

Add-ons extend your monitoring. Frequent Monitoring is priced per domain, while Team Notifications is a flat account-level add-on.

Frequent Monitoring

+$1/domain/month

By default, domains are checked every hour. The Frequent Monitoring add-on lets you mark up to 50 Priority Hosts for checks every 5 minutes.

What changes with this add-on

Priority Hosts keep the default hourly schedule for the rest of the domain intact while giving your most critical hosts a faster 5-minute cadence. Manual checks still include every host.

When to use this

Frequent Monitoring is ideal for production infrastructure where DNS changes carry high risk: payment systems, authentication endpoints, API gateways, or any service where a rogue change could cause a significant outage. The shorter the interval, the sooner you'll know.

How to enable

  1. Open a domain and click Settings.
  2. Toggle Frequent Monitoring on.
  3. Return to the domain page and mark the hosts you want as Priority.
  4. Those hosts start using the 5-minute cadence immediately.

When you disable the add-on, Priority Hosts keep their 5-minute checks until the end of the current billing period, then return to the hourly schedule. Their Priority Host flags are kept, and the add-on drops off your next invoice. On a free trial without a subscription, it turns off right away.

Team Notifications

+$5/month

By default, DNS change alerts are sent to the email address associated with your account. Team Notifications lets you route those notifications to additional destinations, either for every domain on your account or for individual domains.

Supported channels

Slack

Post alerts to any Slack channel. Connect via OAuth, so there's no webhook URL to manage. Change alerts include the old and new value of every changed record.

Discord

Post alerts to a Discord channel. Connect via OAuth, so there's no webhook URL to manage. Change alerts include the old and new value of every changed record.

Generic webhook

Send a structured JSON POST to any HTTPS endpoint for every alert, including DNS changes, outages, and recoveries, each tagged with an event type. Useful for integrating with PagerDuty, custom scripts, or any tool that accepts webhooks.

Additional email addresses

Send alerts to one or more additional email recipients, for example a team alias or an on-call distribution list, in addition to the account owner. Each address must be verified before it receives alerts.

Note

Your account email always receives alerts regardless of whether Team Notifications is enabled. Team Notifications adds destinations on top of the default notification.

How to enable

  1. Click Team Notifications in the sidebar.
  2. Click Enable and confirm.
  3. Under Account-wide channels, click Add channel and add an email address, Slack, Discord (both connected via OAuth), or a generic webhook URL.
  4. Future alerts for your domains are delivered to every configured channel. Email addresses start receiving alerts once they're verified.

Domain-specific channels

Account-wide channels receive alerts for every domain. To also send one domain's alerts somewhere of their own, such as a client's Slack channel, click Add domain channel under Domain-specific channels and pick the domain. You can also add one from the Team Notifications section of the domain's Settings. Domain channels receive alerts in addition to account-wide channels, and a destination set up at both levels gets each alert only once.

Connecting Slack

  1. Click Add channel and select Slack.
  2. Click Connect with Slack and sign in to your Slack workspace.
  3. Choose the channel you want alerts posted to and click Allow.
  4. You'll be redirected back and the channel will appear connected — no URL to copy or paste.

Connecting Discord

  1. Click Add channel and select Discord.
  2. Click Connect with Discord and authorize the connection.
  3. Select the server and channel you want alerts posted to and click Authorize.
  4. You'll be redirected back and the channel will appear connected — no URL to copy or paste.

Generic webhook payloads

Every alert is sent as a POST request with a JSON body. The event field tells you which kind it is:

  • domain_dns_changes_detected: record changes found by a domain's check, grouped by host.
  • dns_change_detected: record changes found when a single host is checked on its own, such as right after you add it.
  • domain_dns_not_answering and domain_dns_answering: a domain's DNS stopped answering, or is answering again.
  • domain_delegation_changed: the registry now lists different nameservers for a domain, as set at its registrar.
  • domain_ds_mismatch: the DS records at the registry match no key the domain's nameservers serve, so DNSSEC is failing.
  • domain_dnssec_changed: DNSSEC was enabled or disabled for a domain at its registrar.
  • test: sent by the Send test button.

A domain's check sends its changes together. The incomplete flag is true when some hosts couldn't be checked, in which case the changes listed are from the hosts that were:

{
  "app": "OneDollarDNS",
  "event": "domain_dns_changes_detected",
  "domain": "example.com",
  "batch_id": "9d6f3c2e-4b1a-4f7e-8c2d-1a2b3c4d5e6f",
  "incomplete": false,
  "timestamp": "2024-01-01T00:00:00.000000Z",
  "hosts": [
    {
      "host_id": 42,
      "host": "example.com",
      "changes": [
        {
          "type": "MX",
          "change": "added",
          "old_value": null,
          "new_value": "10 mail.example.com"
        }
      ]
    }
  ]
}

A single host's changes use the same fields for each change, with domain and host at the top level and a changes array instead of hosts.

A registrar nameserver change lists the nameservers before and after. Either list is empty when the registry listed none:

{
  "app": "OneDollarDNS",
  "event": "domain_delegation_changed",
  "domain": "example.com",
  "parent_zone": "com",
  "old_nameservers": ["ns1.old-dns.com", "ns2.old-dns.com"],
  "new_nameservers": ["ns1.example-dns.com", "ns2.example-dns.com"],
  "timestamp": "2024-01-01T00:00:00.000000Z"
}

A DNSSEC failure lists the registry's DS records in full and the key-signing keys the nameservers serve, which is empty when they serve no keys:

{
  "app": "OneDollarDNS",
  "event": "domain_ds_mismatch",
  "domain": "example.com",
  "parent_zone": "com",
  "ds_records": ["2371 13 2 C988EC423E3880EB8DD8A46FE06CA230EE23F35B578D64E78B29C3E1C83D245A"],
  "nameserver_keys": [{ "key_tag": 40213, "algorithm": 13 }],
  "timestamp": "2024-01-01T00:00:00.000000Z"
}

DNSSEC enabled or disabled lists the registry's DS records before and after in full. old_ds_records is empty when it was enabled, and new_ds_records when it was disabled:

{
  "app": "OneDollarDNS",
  "event": "domain_dnssec_changed",
  "domain": "example.com",
  "parent_zone": "com",
  "old_ds_records": ["2371 13 2 C988EC423E3880EB8DD8A46FE06CA230EE23F35B578D64E78B29C3E1C83D245A"],
  "new_ds_records": [],
  "timestamp": "2024-01-01T00:00:00.000000Z"
}

When DNS stops answering, each affected domain gets its own event, even when one outage hits several domains at once. names lists the domain and any delegated hosts under it that are affected, and reason is one of silent (no nameserver replied), provider_error (the nameservers returned errors) or not_serving (the nameservers refused the zone):

{
  "app": "OneDollarDNS",
  "event": "domain_dns_not_answering",
  "domain": "example.com",
  "names": ["example.com"],
  "reason": "provider_error",
  "nameservers": ["ns1.example-dns.com", "ns2.example-dns.com"],
  "timestamp": "2024-01-01T00:00:00.000000Z"
}

Recoveries use the same shape with domain_dns_answering, with reason saying why it had stopped. Test notifications use a different payload with "event": "test" so your handler can distinguish them:

{
  "app": "OneDollarDNS",
  "event": "test",
  "timestamp": "2024-01-01T00:00:00.000000Z",
  "message": "This is a test notification. Your webhook channel is configured correctly."
}

Testing a channel

Each configured channel has a Send test button (the paper plane icon). Clicking it sends a one-off test notification to that channel immediately, so you can confirm the destination is reachable without waiting for a real DNS change. The delivery status badge updates after the attempt.

Test notifications are limited to 3 per channel per minute. Email channels receive a plain confirmation message; Slack and Discord channels receive a labeled test message; webhook channels receive the test payload shown above.

Delivery status

Team Notifications tracks the latest delivery attempt for each channel, and each channel shows a status badge:

  • Active: receiving alerts.
  • Unverified: an email address that hasn't been confirmed yet.
  • Failing: the latest alert couldn't be delivered.
  • Paused: paused by you, or automatically as described below.
  • Unsubscribed: the recipient used the unsubscribe link in an alert email.

A failed webhook, Slack, or Discord channel does not stop other configured channels from receiving the same alert. Fix the destination URL or webhook configuration, and the status will clear after the next successful delivery.

Pausing channels

To stop a channel's alerts for a while without removing it, click its pause button. Pause all, at the top of the Team Notifications page, pauses every channel at once, account-wide and domain-specific, and channels you add while everything is paused start paused too. Your account email keeps receiving alerts either way. Click Resume all to turn them back on.

Slack, Discord, and webhook channels are also paused automatically when the destination reports that it no longer exists, such as a deleted webhook or an archived Slack channel, and we email you when that happens. For Slack or Discord, remove the channel and connect it again. For a webhook, add the new URL, or resume the channel once the endpoint is back.

Mixing add-ons

Add-ons are independent and can be combined. You can enable Frequent Monitoring on individual domains and Team Notifications once for the whole account.

Related

  • Billing — how add-on costs are calculated and charged.
  • DNS Alerts — what's included in every alert notification.