# DNS Monitoring: Catch Record Changes Early | Uptimeify > Catch unauthorized record changes and mismatches before mail or web go down. DNS auditing for agency portfolios, EU-based. Start your free trial today. Source: https://uptimeify.io/monitoring/domain-monitoring/dns-monitoring An unnoticed zone change takes your clients' mail flow and web access offline long before anyone shouts "server down." Uptimeify checks your portfolio's DNS records continuously against your source of truth. You spot the drift first, not your client. Start Free Trial Look up DNS for Free ## DNS Monitoring. No record hijacking. For the technical stakeholder ### RR-type coverage & resolve triggers That's how it's wired. Read the DNS Monitoring documentation https://docs.uptimeify.io/monitoring/monitoring-types/dns RR types A AAAA MX TXT picked per monitor and checked in a single run. Triggers resolveError mismatch a resolution failure and a content deviation, armed separately. Config Interval and timeout are configurable per monitor. Record Layer ## Complete, not spot-checked. Multi-Record Auditing. One missing or altered record is enough to break mail or web, and nobody notices until the client calls. Uptimeify validates your hostnames' DNS answers on a fixed interval and catches missing critical records and unauthorized changes before they do damage. You watch each zone's integrity, not just whether it resolves. - **A, AAAA, MX and TXT checked together:** So SPF, DMARC and mail routing are covered as one, not one at a time. - **Zone integrity across nameservers:** So a zone stays consistent instead of drifting apart by region. - **Hijacking caught early:** So you see an unauthorized record change before it reaches your client. For the technical stakeholder ### Match mode & mismatch logic That's how it's wired. Read the DNS Monitoring documentation https://docs.uptimeify.io/monitoring/monitoring-types/dns Mode exact contains strict equality vs. substring verification. Source of truth Per RR type you set the expected values the live answer is compared against. Mismatch When the live answer drifts from the stored expectation, the status flips and an incident is raised, separate from a plain resolution error. Scope Expected values are defined per type, independently, not globally. Matching Layer ## Your source of truth, not just any answer. Expected-Value Matching. A DNS answer that resolves isn't automatically the right one. Uptimeify compares your domains' live records against the values you define as expected, and fires the moment they drift. That's how you catch "shadow DNS" and silent misconfigurations a plain reachability check never sees. - **Exact or contains, per record:** So you match strictly or tolerate substrings, record by record. - **Instant incident on drift:** So a change to your source of truth doesn't sit unnoticed for days. - **Rules per record type:** So each type carries its own expectation instead of one blanket check. For the technical stakeholder ### EU node mesh & location targeting That's how it's wired. Read the DNS Monitoring documentation https://docs.uptimeify.io/monitoring/monitoring-types/dns Nodes Checks run from distributed EU nodes; answers are compared across locations for consistency rather than coming from a single source. Targeting allowedCheckCountryCodes scopes a check to specific regions for allowlists or geo-routing. Errors NXDOMAIN Timeout reported as resolution failures, not a content mismatch. Resolution Layer ## Checked by consensus, not guessed from one point. EU-Wide Resolution. What resolves cleanly at one location may already be poisoned or stale at another. Uptimeify checks your records from multiple European nodes and surfaces regional propagation gaps and misconfigurations a single check would miss. You rely on consensus, not on one lucky probe. - **Multiple EU nodes compared:** So local DNS poisoning shows up instead of slipping through. - **Checks scopable to regions:** So you align them with firewall allowlists and routing policies. - **Clear resolution diagnostics:** So on NXDOMAIN or a nameserver timeout you know what's wrong right away. ### SLA & Contract Templates Service Level Agreement templates to define professional boundaries with your clients. ### Pricing Calculator Find the sweet spot for your care plans. Calculate margins based on check frequency and support hours. ### White-Label Pitch Decks Powerpoint Templates that explain 24/7 monitoring to non-technical clients. Close more retainers. ### Churn-Proof Reporting Guide Use automated reports to proactively communicate value, so clients never ask what they're paying for. Claim your Success Kit and start scaling today. Claim your Success Kit & Start Monitoring Ready to turn monitoring into a profit center? Every Uptimeify subscription includes access to our Success Kit, a collection of battle-tested resources to turn your monitoring into a profit center. ## We don't just monitor. We help you sell. → For the technical stakeholder ### Resolve error vs. mismatch: how it's wired Uptimeify separates two failure classes cleanly: a `resolveError` (NXDOMAIN, nameserver timeout, no record) means resolution itself failed; a `mismatch` means an answer came back but drifts from your stored expectation. Each fires its own trigger and is armed per monitor independently. The match mode (`exact` or `contains`) applies per RR type, and expected values are defined per type independently, so you tell "broken" apart from changed" instead of lumping them together. Why do you need DNS monitoring when the server is online? Because a reachable server says nothing about your DNS integrity. A changed MX record halts mail delivery; a wrong A record sends visitors nowhere, all while the server runs. DNS monitoring checks that exact layer, so you catch an outage a plain [uptime check](/monitoring/website-monitoring/uptime-monitoring) can't see. How does matching against a source of truth protect you from hijacking? You store your records' expected values as the intended state; Uptimeify compares every live answer against it and fires the moment it drifts. An unauthorized record change stands out as it happens, not once your client's traffic has already been redirected. How does monitoring TXT and MX records protect your clients deliverability? TXT carries SPF and DMARC, MX drives mail routing. If either slips, mail lands in spam or nowhere. Uptimeify watches both against your expected values, so you fix a broken mail setup before it takes down your client's communication. Which locations is DNS resolution checked from? From multiple European nodes whose answers are compared against each other. Optionally, you scope the check to specific regions. That's how you catch regional propagation issues and local poisoning instead of trusting a single vantage point. Is the data processed in the EU? Yes. Uptimeify is operated in Frankfurt, on European infrastructure, with no US sub-processor with access to your customer or monitoring data. That minimizes the risk around third-country transfers and takes a whole discussion off the table in B2B and public-sector pitches. FAQ ## Frequently Asked Questions Catch record mismatches and hijacking attempts before they hit your clients' mail or web, EU-checked, against your own source of truth, set up in minutes. ## Ready to lock down your portfolio's DNS integrity?