DNS
DNS check helps control the composition of DNS records and detect discrepancies between NS servers.
This task type requires PRO tariff.
When to use
- When it's important to monitor DNS after site migration, contractor change, or email migration.
- When you want to detect record discrepancies between NS servers in time.
When to choose another type
- If you need site availability, not DNS configuration control, use HTTP.
- If you don't know the reference record values, don't enable strict mode unless necessary.
Note:
Strict mode is useful only when you exactly know what the records should be now.
If DNS changes as part of regular balancing, CDN, or migration, start with NS server comparison mode.
Form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Name | Name of the check in the list and notifications. | Specify for which domain the DNS records are being checked. | DNS for example.com |
| Group | Allows assigning the task to a project or section. | Select a group if you want to keep project tasks together. | Main project |
| Host | Domain whose DNS records need to be checked. | Specify the domain without protocol and path. | example.com |
| NS, IP, CNAME, MX, SOA check mode | For each record type, you can disable checking, compare responses between NS servers, or require strict match with your values. | Select the mode separately for each record type that matters to you. | Check only record consistency between NS servers |
| NS, IP, MX lists | Reference values for strict mode. | Specify one value per line only if strict mode is selected. | ns1.example.com ns2.example.com |
| CNAME address | Reference CNAME value for strict mode. | Specify one domain name without protocol. | target.example.net |
| SOA record serial number | Reference serial value for strict SOA mode. | Fill only if you really control a specific serial value. | 2026031601 |
| Interval | How often to check DNS records. | Leave the default value or increase for rarely changing zones. | 1 hour |
| Notification channels | Where to send problem and recovery messages. | Check the channels where you actually read notifications. | Telegram and email |
| Reports | Periodic task summaries. | Enable if you want to receive an overview without manual panel login. | Weekly report |
When the alert will come
An alert will come if the enabled DNS checks show discrepancies between NS servers or records stop matching the specified reference.
Notification settings
For each notification channel in the task, you can set additional parameters. They apply only to DOWN events.
| Parameter | What it does |
|---|---|
| Enabled | Allows or prohibits sending notifications via this channel for this task. |
| Delay for PRO | Delays the first DOWN notification for the selected time (up to 12 hours). Convenient to avoid alerts for short-term failures. |
| Repeat after PRO | Periodically repeats the notification while the task remains in DOWN status (up to 1 hour between repeats). Suitable when it's important not to miss a prolonged failure. |
"Delay" and "Repeat" parameters do not affect UP events and recovery notifications.