OneDollarDNS
OverviewGetting StartedHow It WorksDNS AlertsAdd-onsBillingFAQ

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.

Disabling the add-on reverts all hosts to the default hourly check schedule while preserving any Priority Host flags. Billing adjusts automatically at the next billing cycle.

Team Notifications

+$5/mo

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 across your account for all monitored domains.

Supported channels

Slack webhook

Post alerts to any Slack channel using an Incoming Webhook URL. The message includes the domain, host, record type, change type, and old/new values formatted as a Slack Block Kit message.

Discord webhook

Post alerts to a Discord channel using a Discord Incoming Webhook URL. Each change appears as a rich embed with the record type, change type, and old/new values.

Generic webhook

Send a structured JSON POST to any HTTPS endpoint. The payload includes the event type, domain, host, timestamp, and an array of changes — 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. Open Settings and click Notifications.
  2. Toggle Team Notifications on.
  3. Add one or more channels — email addresses, Slack webhooks, Discord webhooks, or generic webhook URLs.
  4. Save. Future alerts for your domains will be delivered to all configured channels.

Setting up a Slack webhook

  1. In Slack, go to Apps and search for Incoming Webhooks.
  2. Click Add to Slack and choose the channel to post to.
  3. Copy the generated Webhook URL.
  4. In Team Notifications, click Add channel, select Slack, and paste the URL.

Setting up a Discord webhook

  1. In Discord, open the channel settings and go to Integrations → Webhooks.
  2. Click New Webhook, name it, and copy the Webhook URL.
  3. In Team Notifications, click Add channel, select Discord, and paste the URL.

Generic webhook payload

When a DNS change is detected, a POST request is sent to your URL with a JSON body: 

{
  "event": "dns_change_detected",
  "domain": "example.com",
  "host": "sub.example.com",
  "timestamp": "2024-01-01T00:00:00Z",
  "changes": [
    {
      "type": "MX",
      "change": "added",
      "old_value": null,
      "new_value": "mail.example.com"
    }
  ]
}

Delivery status

Team Notifications tracks the latest delivery attempt for each channel. Channels show a Delivered badge after a successful send, or a Failed badge when the latest attempt could not be delivered.

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.

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.