Skip to main content
Network

DNS Resolution

Check that hostnames resolve on the device quickly and to the expected IP address.

The DNS Resolution check resolves hostnames through the device's resolver, the same way other programs on the device do. It reports when a name cannot be resolved, a lookup takes too long, or an expected IP address is missing. The check runs on the device with the octoja agent on Windows, Linux, and macOS (each in x64 and Arm64 builds), every 5 minutes by default.

Steps

  1. Open the device.
  2. Choose Checks → Add Check → DNS Resolution.
  3. Enter the names to resolve under Hostnames and adjust the other fields if needed.

To cover several devices, assign the check with a config package.

Settings

FieldTypeRequiredDefaultDescription
Hostnameslist of stringsYes—Hostnames to resolve, e.g. example.com
Expected address (optional)stringNo—If set, the answer for every hostname must include exactly this IP address
Timeout (ms)integerNo5000Time allowed per hostname. Values outside 500–60000 are clamped

Thresholds

FieldTypeRequiredDefaultDescription
Warning lookup time (ms)integerNo500Warning when resolving a hostname takes at least this long
Error lookup time (ms)integerNo2000Critical when resolving a hostname takes at least this long
  • Expected address (optional) applies to every hostname in the check. The address is compared as a complete IP address, not as a substring. If you need different expected addresses, create one check per address.
  • If Warning lookup time (ms) is greater than Error lookup time (ms), the check swaps the two values before evaluation.
  • Up to ten hostnames are resolved at the same time. Blank entries are ignored, and leading and trailing spaces are removed.

Results

Every hostname is graded on its own. The check reports the worst result across all hostnames.

Condition (per hostname)ResultShown as
The name resolves, includes the expected address if one is set, and the lookup time stays below Warning lookup time (ms)OKAddresses and lookup time
The lookup time reaches Warning lookup time (ms)WarningAddresses and lookup time
The lookup time reaches Error lookup time (ms)CriticalAddresses and lookup time
The expected address is not among the addressesCriticalExpected address not found
The lookup returns no addressesCriticalNo addresses returned
The resolver reports an error, for example because the name does not existCriticalCould not resolve (NXDOMAIN)
The lookup takes longer than Timeout (ms)CriticalLookup timed out
Unexpected error during executionErrorError message
No hostnames configuredWarningNo hostnames monitored.

A missing expected address is evaluated before the lookup time: such a hostname is Critical even if it resolved quickly.

Per hostname, the check reports:

  • Whether the name resolved
  • Up to eight distinct returned addresses
  • The lookup time in milliseconds
  • Whether the expected address was found, if one is configured
  • The result and, where one applies, the reason

The expected-address comparison considers every returned address, even though only the first eight are shown.

Notes

The check uses the operating system's resolver and therefore the device's DNS settings. It shows whether names resolve on this device. To query a specific DNS server or a specific record type such as MX or TXT, use the NSLookup check.

See also: Set up alerts for a check