Set up DNS monitoring: How to keep tr...
10 Jul 2026
Set up DNS monitoring: How to keep track of your domain
A website can be technically flawless and yet still be unreachable for your visitors. If the DNS records are incorrect, a domain no longer resolves properly or points to the wrong IP address, the browser cannot reliably find the relevant web server. With DNS monitoring you regularly check whether your domain can be resolved correctly, which DNS records are returned and whether important values remain correct. This lets you detect DNS problems early, before visitors can no longer reach your website or e-mail services are disrupted. In this article you will find out exactly what DNS monitoring is, which errors you can uncover with it and how to set up the monitoring step by step with Hosttest Plus.
Author:
Christopher | 10 Jul 2026
Christopher | 10 Jul 2026
via Gemini
In a Nutshell
DNS monitoring continuously monitors name resolution, central DNS records and nameserver response times to detect availability issues and unexpected changes at an early stage. It complements HTTP, SSL and port monitoring and enables targeted alerting when values deviate from defined thresholds.
- Key checkpoints: reachability of domain resolution, A/AAAA/CNAME/MX/TXT/NS records, TTL compliance, as well as nameserver response times and response integrity.
- Typical detection cases: incorrect IP assignments after server changes, missing or faulty MX/TXT records, unexpected record changes and slow or non-responsive nameservers.
- Best practice: define expected thresholds, configure check intervals and alert channels, and correlate DNS checks with HTTP/SSL/ping/port monitoring for faster root-cause analysis.
DNS Monitoring
DNS Monitoring: Reliably monitor availability and DNS records
A website can function perfectly on the server and still be inaccessible to visitors. DNS monitoring regularly checks whether your domain resolves correctly, whether important DNS records are present, and whether they continue to point to the correct destination.
🌐
When the domain no longer points to the website
A website can run perfectly on the actual server and still be inaccessible to visitors. This happens, for example, when the domain no longer resolves correctly or points to an incorrect IP address. To visitors it then appears as if the website has failed, even though the web server is still active.
DNS issues are particularly tricky because they do not always originate on the website itself. The hosting package may be functioning and the website files may be fully present, yet the domain no longer leads to the correct destination.
Basics
What is the Domain Name System?
The Domain Name System, or DNS, is a central component of the Internet. It ensures that people can use easily memorable domain names while computers work in the background with technical addresses.
Enter a domain
Visitors enter a domain such as beispiel.de into the browser. For the website to load, the technical address must first be determined.
Query DNS servers
The browser or operating system queries a DNS server. It returns the appropriate technical address, usually an IP address.
Access the website
Only after DNS resolution can the browser establish a connection to the actual web server and load the website.
📘
DNS as the Internet's address directory
Put simply, DNS works like an address directory. The visitor knows the name of the website; DNS provides the corresponding technical address. If this address directory returns incorrect, outdated or no information at all, the website cannot be reached correctly.
Monitoring
What is DNS monitoring?
DNS monitoring regularly checks whether a domain's name resolution is functioning as expected. It verifies whether specific DNS records exist, what values they return and whether the responsible name servers are reachable.
Can the domain be resolved?
The monitoring checks whether the domain can be resolved at all and whether a valid response is returned.
Are records correct?
Important DNS records such as A, AAAA, CNAME, MX, TXT or NS can be monitored specifically.
Are values unchanged?
DNS monitoring can detect whether the returned values still match the expected data.
Are the name servers reachable?
The responsible name servers can also be monitored, as they are crucial for DNS resolution.
Detect changes
Unexpected changes to DNS records can be detected early, before visitors or systems are affected.
Check response times
Slow DNS responses can delay page loading. Such anomalies can also be detected more easily through monitoring.
Why is it important?
Why DNS monitoring is important for website owners
DNS is a technical foundation that often receives little attention during normal operation. As long as everything works, visitors do not notice it. However, once DNS problems occur, the impact can be significant.
Without DNS monitoring
- DNS errors often only become apparent through visitors, customers or support requests.
- The website can appear unreachable even though the web server is running.
- Subdomains, email services or external applications can fail unnoticed.
- Incorrect entries after migrations or changes can persist for longer.
- Troubleshooting may start in the wrong place.
With DNS monitoring
- You can detect early on whether a domain resolves correctly.
- Important DNS records can be monitored specifically.
- Unexpected changes become visible more quickly.
- Errors after domain migrations or server changes can be better managed.
- DNS checks support root-cause analysis for website and email problems.
Impact
What DNS issues can cause
A reachable web server alone is not enough if visitors cannot find its address. The domain must resolve correctly so the browser knows which server to connect to.
01
Without DNS, the domain won't work
If DNS resolution is disrupted, the website may not be reachable or only partially accessible. To visitors this appears as a typical website outage. In reality, the issue may not be the web server but the mapping between the domain and the server.
02
DNS errors often affect multiple services
DNS is not only relevant for loading the website. DNS also controls email services, subdomains, APIs, webmail access, CDN services and external verifications.
- Website and subpages
- Email reception and sending
- Subdomains and customer portals
- APIs and webhooks
- Webmail and external services
- CDN or security services
03
DNS changes can go unnoticed
DNS records are often changed infrequently. For that reason, errors can go unnoticed for a long time if no automatic monitoring is in place.
- accidentally deleted records
- incorrectly transferred values
- typos in IP addresses or hostnames
- changes made by third parties
- subdomains not configured correctly
- outdated records after a server migration
04
Errors frequently occur after migrations and changes
Periods when work is being done on the technical infrastructure are particularly prone to DNS problems. This includes domain transfers, hosting changes, new nameservers, a CDN change or migrating to a new server.
DNS records
Which DNS records are important for website operators?
Several types of DNS record are relevant for website operators. Not every DNS record directly affects accessing the website, but many influence the availability or functionality of certain services.
| DNS record | What it's used for | Why it should be monitored |
|---|---|---|
| A Record | Links a domain or subdomain to an IPv4 address. | If the record points to the wrong IP address, visitors will end up on the wrong server or cannot reach the website. |
| AAAA Record | Points to an IPv6 address. | A faulty AAAA record can affect users with IPv6 connections even if IPv4 works. |
| CNAME Record | Points one hostname to another hostname. | Important for www variants, subdomains, external services, e-commerce platforms or landing pages. |
| MX Record | Specifies which mail servers accept emails for a domain. | Missing or incorrect MX records can disrupt incoming email. |
| TXT Record | Used for SPF, DKIM, DMARC and external domain verifications. | Faulty TXT records can affect email delivery or verification of external services. |
| NS Record | Defines which nameservers are authoritative for a domain. | If NS records are incorrect or nameservers are unreachable, the entire DNS resolution can be affected. |
Failure scenarios
Which problems does DNS monitoring detect?
DNS monitoring can make different types of faults visible. Some of these lead directly to a website outage, others affect specific services, subdomains or email functions.
Domain not resolvable
If a domain cannot be resolved at all, the browser receives no IP address. The website is then effectively unreachable.
Incorrect IP address
After a server migration, an old or incorrect A Record can cause visitors to continue reaching the old server or an incorrect target environment.
Unexpected changes
DNS records can be accidentally modified, deleted or overwritten. Monitoring helps to detect such deviations more quickly.
Slow nameservers
If nameservers are slow or fail to respond, the entire website load can be delayed or may fail.
Missing records
Individual records can be missing even though the main domain functions. This often affects www, API subdomains, MX Records or TXT verifications.
Problems after changes
Hosting migrations, domain transfers, CDN activations or new mail providers are typical situations where DNS errors can occur.
Process
How does DNS monitoring work?
In DNS monitoring the monitoring system regularly makes a DNS query for the monitored domain or a specific record. The response is evaluated and compared with the expected data.
1
Send a DNS query
The monitoring system regularly queries the domain or a specific DNS record.
2
Check name server response
The authoritative name servers return a response, which is then evaluated.
3
Read DNS value
The returned DNS record is read, for example an IP address, a mail server or a TXT value.
4
Compare with expected value
The monitoring checks whether the current value matches the expected value.
5
Check response time
Additionally, it can check how quickly the DNS resolution occurs.
6
Trigger notification
In case of discrepancies, missing records or outages an alert can be triggered.
DNS changes
What do DNS propagation and TTL mean?
DNS changes are not always visible everywhere immediately. This is because DNS responses are cached in many places.
DNS propagation
After a change, different users may temporarily receive different results. Some will already see the new record, while others still get the old value. This period is commonly referred to as DNS propagation.
TTL
TTL stands for Time to Live. It indicates how long a DNS record may be cached before it must be queried again.
Short TTL
A short TTL ensures that changes can become visible more quickly. This is particularly helpful before a server migration or a planned changeover.
Long TTL
A long TTL reduces the number of DNS queries and can relieve load on name servers. However, changes then take longer to propagate everywhere.
In practice
Which DNS records should be monitored?
Which records should be monitored depends on the website and the services used. For many projects, checking only the primary domain is not sufficient.
A record
Important for the primary domain and traditional IPv4 reachability.
AAAA record
Useful if the website should also be reachable over IPv6.
www CNAME
Important if the www variant points to a target via a CNAME.
NS records
Determines which nameservers are responsible for the domain.
Subdomains
For example: shop, portal, app, webmail, API or staging systems.
MX records
Particularly important if the domain is used for business email.
TXT records
Relevant for SPF, DKIM, DMARC and external domain verifications.
External services
CNAME or TXT records for CDN, newsletters, search engines, shops or cloud services.
Checklist
What to do in the event of a DNS alert?
When a DNS alert occurs, first check which record is affected and whether any changes were made shortly beforehand. Not every discrepancy is automatically an error.
Initial checks
- Check the domain status at the registrar
- Check the authoritative nameservers
- Access the DNS zone in the provider's customer panel
- Compare the expected IP address with the current record
- Check for recent changes
- Consider TTL and possible caching
Further checks
- Test the www variant and important subdomains separately
- Check MX records for email issues
- Check TXT records for external services and email authentication
- Contact the web host, registrar or DNS provider
- Then re-test DNS resolution
💡
DNS change or an actual error?
It is important to distinguish between an actual error and an ongoing DNS change. If the TTL was previously set high, old values may remain cached for some time.
Context
Limitations of DNS monitoring
DNS monitoring shows whether name resolution works and whether important DNS records return the expected values. However, it does not automatically confirm that the website is being served correctly from the target server.
DNS monitoring primarily detects
- failed DNS resolution
- missing or incorrect DNS records
- unexpected changes to DNS records
- problems with nameservers
- deviations from expected target values
- slow DNS response times
Not automatically checked
- whether the web server serves the website correctly
- whether the website application functions correctly
- whether an SSL certificate is valid
- whether forms, logins or checkout processes work
- whether the actual page content is displayed correctly
Combination
Combine DNS monitoring with other checks
Use website monitoring tools to check the different technical layers with various types of monitoring. This separation is particularly helpful when troubleshooting.
DNS Monitoring
Checks whether the domain resolves correctly and points to the expected target.
Ping Monitoring
Checks whether the target system is reachable over the network.
Port Monitoring
Checks whether a specific network service is reachable, for example port 80 for HTTP or port 443 for HTTPS.
HTTP Monitoring
Checks whether the website itself is reachable, what status code the web server returns and how quickly it responds.
SSL Monitoring
Monitors the secure HTTPS connection and the validity of the certificate.
Better root-cause analysis
If DNS works and the server is reachable by ping but HTTP fails, the problem is likely with the web server or the website application. If DNS already fails, the domain configuration should be checked first.
HOSTtest Plus
DNS monitoring with HOSTtest Plus
With HOSTtest Plus you can centrally monitor important DNS records and the availability of name resolution. You can check whether a domain continues to resolve correctly and whether the expected DNS values are returned.
This helps detect issues more quickly that would not be apparent on the web server itself. A central overview is particularly useful when managing multiple domains, subdomains or client projects, to keep important records under observation.
DNS monitoring
Checks domain resolution, DNS records and expected values.
HTTP monitoring
Monitors availability, status code and response time.
SSL monitoring
Monitors certificates, expiry dates and HTTPS connections.
Ping monitoring
Checks basic network reachability.
Port monitoring
Monitors important services and network ports.
Keyword monitoring
Checks whether the expected content is served.
Step by step
How to use HOSTtest Plus as a DNS monitoring tool
A DNS monitor can be set up quickly in HOSTtest Plus. After logging in, create a new monitor, choose the appropriate monitoring type and then specify which domain or DNS record should be checked regularly.
1
Create an account or log in
First create a free HOSTtest Plus account or log in with your existing credentials.
2
Create a new monitor
Open the menu section Pulse → Monitors. There you can create an individual monitor for your domain, subdomain or a specific DNS record.
Screenshot: Creating a new DNS monitor in HOSTtest Plus
3
Select DNS as the monitor type
Select DNS as the monitor type. This tells HOSTtest Plus to check whether the configured domain or chosen DNS record resolves as expected.
4
Enter the domain and DNS record
Enter the domain or subdomain to monitor and specify which DNS record should be checked. Depending on the goal, records such as A, AAAA, CNAME, MX, TXT or NS may be relevant.
5
Specify expected value and check interval
Enter the expected DNS value, for example a specific IP address, a mail server or a TXT value, and choose the desired check interval.
6
Configure notifications
Choose how you want to be notified in the event of a failed DNS resolution, an unexpected change or a missing record.
7
Activate DNS monitoring
Activate DNS monitoring by clicking “Create monitor”. From that point, HOSTtest Plus will automatically check your DNS configuration at the set interval.
Screenshot: Status and evaluation of your DNS monitor
✅
Conclusion: DNS monitoring protects against invisible availability issues
DNS is a central foundation for the availability of websites, email services, subdomains and many external applications. If name resolution fails or points to the wrong target, visitors and systems cannot reliably reach the desired services.
The problem is not always on the web server itself. A website can run perfectly from a technical perspective, while the domain is misconfigured or important DNS records are missing.
DNS monitoring makes such errors visible. It regularly checks whether domains are resolved correctly, whether important records are present and whether the expected values are returned. This makes it an important component for reliable website monitoring and a sensible complement to HTTP monitoring and SSL monitoring.
Write a comment
- Monitoring
Tags for this article
More web hosts
More interesting articles
Website not reachable - Causes and Measures
Anyone who operates their own website for a longer period of time will sooner or later be confronted with downtime. But ...
Server Outage - Prevention and Immediate Measures
A server outage is the worst possible news for a company. We show what can and should be done.
HOSTtest Plus: Free Website Monitoring for Webmasters, Agencies, and Businesses
Websites must be accessible at all times today. Just a few minutes of downtime can cost visitors, enquiries, and revenue...
Uptime and Downtime in Web Hosting Offers
If you are looking for a suitable web hosting provider, you will quickly come across information about the uptime or dow...
Monitor websites for free: A comparison of free website monitoring tools
In this article we look at the best-known free website monitoring tools and compare which features they offer in their f...
Set up HTTP monitoring: keep an eye on your website
A website can exist technically and still not function correctly for visitors. HTTP monitoring regularly checks whether ...
Media Partner:
