DNS Monitoring
DNS Monitoring checks the reachability of the targets behind your DNS records and shows the result directly in the smoxy interface. It helps you spot basic availability issues with the services your records point to.
What is DNS Monitoring?
As soon as you create DNS records in smoxy, the platform automatically attempts to reach the target address of each record and shows you whether the connection was successful. This makes it easy to confirm that records are working — or to catch misconfigurations early.
What does smoxy monitor?
smoxy regularly checks whether the target of a DNS record is reachable — for example, whether a server responds at the configured IP address. The status appears next to the record in the DNS overview.
Monitoring covers basic reachability only. It does not perform application-level checks (no HTTP status validation, no port scan, no TLS verification).
Test Frequency
DNS monitoring runs at a fixed interval of 30 seconds per IP address. The interval is not configurable.
For each check, three queries are sent in parallel from different regions worldwide:
- If at least one region responds successfully, the record is considered online.
- If all three queries fail, the record is marked offline.
Where the Status Is Displayed
Open a domain in smoxy and switch to the DNS Records tab. Records that are monitored show a color-coded status:
- 🟢 Reachable
- 🔴 Not reachable
The displayed state reflects the most recent check.
Notifications
There are no notifications, no history of past checks, and no escalation. DNS Monitoring is a visual aid in the DNS overview, not an alerting system. Pair it with an external uptime monitor if you need notifications.
Caveats
- Results can be skewed by local network restrictions or firewalls between smoxy's checking infrastructure and your target.
- "Not reachable" means smoxy didn't receive a successful response — it does not always mean the service is down.
- Only basic reachability is checked; a record may be marked online even if the application running behind the IP is broken.