Detect DNS changes, hijacking and misconfiguration automatically. This guide covers DNS monitor setup, supported record types (A, AAAA, MX, TXT, CNAME, NS) and practical examples for UK businesses protecting their .co.uk domains.
Why monitor DNS • How DNS monitoring works • Setting up a DNS monitor • Supported record types • Practical examples • FAQ
DNS is the foundation of every online service. It translates domain names into IP addresses, routes email to mail servers, and validates domain identity through SPF and DKIM. When DNS goes wrong, everything breaks — websites unreachable, email stops arriving, SSL certificate validation may fail.
Common DNS problems:
Uptime Kuma resolves a hostname for a specific record type and compares the result against an expected value. If matches, up. If differs or query fails, down + notifications.
You can specify a custom DNS server (8.8.8.8 or 1.1.1.1). Important because your local resolver might cache an old value while the rest of the world sees the changed record. Using a public resolver ensures you’re checking what external visitors experience.
Matching conditions:
Leave Expected Value empty to simply check the query returns a valid response (detects record deletion).
mybusiness.co.uk185.199.108.153)Tip: always use a public DNS resolver for monitoring — gives an external perspective and avoids false results from local caching.
| Type | Purpose | Example expected |
|---|---|---|
| A | Domain to IPv4 address | 185.199.108.153 |
| AAAA | Domain to IPv6 | 2606:50c0:8000::153 |
| MX | Email routing to mail server | mail.mybusiness.co.uk |
| TXT | SPF, DKIM, domain verification | v=spf1 include:_spf.google.com ~all |
| CNAME | Alias one domain to another | mybusiness.co.uk.cdn.cloudflare.net |
| NS | Authoritative nameservers | ns1.example.com |
| CAA | Certification Authority authorisation | letsencrypt.org |
| SOA | Zone authority configuration | (typically not matched by value) |
www.mybusiness.co.uk, Record Type: A, Expected: 185.199.108.153If anyone changes your A record, you’re alerted immediately.
mybusiness.co.uk, Record Type: MX, Expected: mail.mybusiness.co.ukSPF records authorise IPs to send mail on your domain’s behalf. If missing or changed, email may be rejected or spammed.
mybusiness.co.uk, Record Type: TXTv=spf1 with contains conditionGood to know: DNS changes take propagation time (minutes to hours, TTL-dependent). Set retries to 2–3 to allow legitimate changes to propagate before alerting.
Protect your UK domains with DNS monitoring
SmartXHosting Uptime Kuma Hosting watches your .co.uk A, MX and SPF records round the clock — alerting on hijacking, misconfiguration or accidental changes.
Q: What record types can Uptime Kuma monitor?
A: A, AAAA, MX, TXT, CNAME, NS, SOA, SRV, PTR, CAA.
Q: How does monitoring detect hijacking?
A: Expected value check. If someone changes the A record to point elsewhere, resolved value no longer matches — Uptime Kuma alerts.
Q: Should I use a custom DNS server?
A: Yes. Public resolver like 8.8.8.8 or 1.1.1.1 gives external perspective and avoids local caching issues.
Q: Can I monitor SPF and DKIM?
A: Yes — TXT record type with contains condition checking for key prefix (v=spf1 or v=DKIM1).
Q: How many DNS monitors for a UK business?
A: Typically 3–5: A record for website, MX for mail, TXT for SPF, optionally DKIM and DMARC. Each costs zero extra on unlimited-monitor plans.