Contabo unveils a new VPS portfolio
13 Aug 2026
Set up DNS monitoring: Keep an eye on your domain
A website can be technically flawless and still be unreachable for your visitors. If DNS records are incorrect, a domain no longer resolves properly or points to the wrong IP address, the browser will not reliably find the responsible 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 way you detect DNS problems early, before visitors can no longer reach your website or email services are disrupted. In this article you will learn exactly what DNS monitoring is, which errors you can uncover with it and how to set up 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 for deviations from defined thresholds.
- Key checkpoints: availability of domain name 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 migrations, 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 unreachable for visitors. DNS monitoring regularly checks that your domain resolves correctly, that essential DNS records are present and that they continue to point to the correct destination.
🌐
When a domain no longer points to the website
A website can run flawlessly on the actual server and still be unreachable for visitors. This can happen, for example, when the domain no longer resolves correctly or points to an incorrect IP address. To visitors it then appears as though the website has gone down, even though the web server remains active.
DNS problems are particularly insidious because they do not always originate on the website itself. The hosting package can be functioning, the website files can be fully present and 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 allows people to use easily memorable domain names while computers work with technical addresses in the background.
Enter a domain
Visitors enter a domain like beispiel.de into the browser. For the website to load, the technical destination 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.
Load the website
Only after DNS resolution can the browser connect 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 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 working as expected. It verifies that specific DNS records exist, what values they return, and whether the authoritative nameservers are reachable.
Is the domain resolvable?
Monitoring checks whether the domain can be resolved at all and whether a valid response is returned.
Are the records correct?
Important DNS records such as A, AAAA, CNAME, MX, TXT or NS can be specifically monitored.
Are the values unchanged?
DNS monitoring can detect whether the returned values still match the expected data.
Are the nameservers reachable?
The authoritative nameservers 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 website loading. Such anomalies can also be identified more effectively through monitoring.
Why it matters
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 notice nothing. However, once DNS issues occur, the impact can be significant.
Without DNS monitoring
- DNS errors often only come to light through reports from visitors, customers or support.
- The website can appear unreachable even though the web server is running.
- Subdomains, email services or external applications can fail without being noticed.
- Incorrect records after migrations or changes can persist for longer.
- Troubleshooting may start in the wrong place.
With DNS monitoring
- You can detect early whether a domain is resolving correctly.
- Important DNS records can be monitored selectively.
- Unexpected changes are detected more quickly.
- Issues following domain migrations or server changes can be managed more effectively.
- DNS checks support root-cause analysis of website and email problems.
Impact
What DNS problems can cause
A reachable web server alone is not enough if visitors cannot resolve its address. The domain must be resolved correctly so the browser knows which server to connect to.
01
Without DNS the domain will not work
If DNS resolution is disturbed, the website may be inaccessible or only partially reachable. To visitors this looks like a typical website outage. In reality, however, the problem is not necessarily the web server but the mapping between domain and server.
02
DNS errors often affect multiple services
DNS is not only relevant for loading websites. DNS also controls email services, subdomains, APIs, webmail access, CDN services and external verifications.
- Website and subpages
- Inbound and outbound email
- 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 undetected for a long time if no automatic monitoring is in place.
- Accidentally deleted records
- Incorrectly copied values
- Typos in IP addresses or hostnames
- Changes by third parties
- Improperly configured subdomains
- Outdated records after a server migration
04
Errors often occur after migrations and changes
Periods during which technical infrastructure is worked on are particularly prone to DNS issues. These include domain transfers, hosting migrations, new nameservers, a CDN change or moving to a new server.
DNS records
Which DNS records are important for website operators?
Several types of DNS records are relevant for website operators. Not every DNS record directly affects the website request, but many influence the reachability or function of specific services.
| DNS record | What it is 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 reach the wrong server or be unable to access the website. |
| AAAA record | Points to an IPv6 address. | A misconfigured AAAA record can affect users on 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 email for a domain. | Missing or incorrect MX records can disrupt email reception. |
| TXT record | Used for SPF, DKIM, DMARC and external domain verifications. | Incorrect TXT records can impair email delivery or verifications by external services. |
| NS record | Specifies which nameservers are authoritative for a domain. | If NS records are incorrectly set or nameservers are unreachable, the entire DNS resolution can be affected. |
Error scenarios
What problems does DNS monitoring detect?
DNS monitoring can reveal different types of faults. Some of these lead directly to a site outage, others affect specific services, subdomains or email functionality.
Domain not resolvable
If a domain cannot be resolved at all, the browser does not receive a technical destination address. The website is then effectively unreachable.
Incorrect IP address
After a server change, an old or incorrect A record can cause visitors to continue landing on 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 respond slowly or not at all, the entire website request can be delayed or fail.
Missing records
Individual records may be missing even though the main domain works. 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?
With DNS monitoring, the monitoring system regularly performs a DNS query for the monitored domain or a specific record. The response is evaluated and compared with the expected data.
1
Make a DNS query
The monitoring system regularly queries the domain or a specific DNS record.
2
Check nameserver response
The authoritative nameservers 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 (MX) or a TXT record.
4
Compare with expected value
The monitoring checks whether the current value matches the expected one.
5
Check response time
Additionally, it can check how quickly 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 immediately visible everywhere. This is because DNS responses are cached in many places.
DNS propagation
After a change, different users may temporarily receive different results. Some 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 especially 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 take effect everywhere.
Use cases
Which DNS records should be monitored?
Which records should be monitored depends on the respective website and the services used. For many projects, checking only the main domain is not sufficient.
A Record
Important for the main domain and traditional IPv4 reachability.
AAAA Record
Useful if the website should also be accessible via IPv6.
www-CNAME
Important if the www variant uses a CNAME to point to a target.
NS Records
Crucial for which nameservers are authoritative 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 CDNs, newsletters, search engines, shops or cloud services.
Checklist
What to do in a DNS alert?
In the event of a DNS alert, first check which record is affected and whether any changes were made shortly beforehand. Not every deviation is automatically an error.
Initial checks
- Check the domain status with the registrar
- Check the authoritative nameservers
- Open the DNS zone in the provider's customer control panel
- Compare the expected IP address with the current record
- Check for recent changes
- Take TTL and possible caching into account
Further checks
- Test the www variant and important subdomains separately
- Check MX records if there are email issues
- Check TXT records for external services and email authentication
- Contact the web host, registrar or DNS provider
- Then test DNS resolution again
💡
DNS change or a genuine error?
It is important to distinguish between an actual error and an ongoing DNS change. If the TTL was previously set high, old values can remain cached for a while.
Context
Limits 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 records
- problems with nameservers
- deviations from expected target values
- slow DNS response times
Not checked automatically
- whether the web server is serving the website correctly
- whether the website application works 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 test the different technical layers with various types of monitoring. This distinction is especially helpful when troubleshooting.
Keyword Monitoring
Checks whether a website's content is displayed correctly.
Ping Monitoring
Checks whether the target system is generally reachable over the network.
Port Monitoring
Checks whether a specific network service is accessible, 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.
Improved root cause analysis
If DNS is working and the server is reachable via ping, but HTTP fails, the problem is likely with the web server or the web application. If DNS is already failing, check the domain configuration 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 is still resolving correctly and whether the expected DNS values are returned.
This helps detect issues more quickly that would not be visible on the web server itself. Especially with multiple domains, subdomains or client projects, a central overview is useful to keep important records in sight.
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 that 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 a custom monitor for your domain, subdomain or a specific DNS record.
Screenshot: Creating a new DNS monitor in HOSTtest Plus
3
Select DNS as monitor type
Choose DNS as the monitor type. HOSTtest Plus will then check whether the configured domain or selected DNS record resolves as expected.
4
Enter domain and DNS record
Enter the domain or subdomain to be monitored and specify which DNS record should be checked. Depending on the aim, records such as A, AAAA, CNAME, MX, TXT or NS may be relevant.
5
Set 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
Specify how you want to be notified in case of a failed DNS resolution, an unexpected change or a missing record.
7
Activate DNS monitoring
Switch DNS monitoring live by clicking "Create monitor". From that point, HOSTtest Plus will automatically check your DNS configuration at the specified interval.
Screenshot: Status and analysis 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 destination, visitors and systems cannot reliably reach the intended services.
The problem is not always with the web server itself. A website can be technically flawless while the domain is incorrectly configured or important DNS records are missing.
DNS monitoring makes such errors visible. It regularly checks whether domains are correctly resolved, whether important records are present and whether the expected values are returned. This makes it an important component of reliable website monitoring and a useful complement to HTTP monitoring and SSL monitoring.
Write a comment
- Monitoring
Tags for this article
More web hosts
More interesting articles
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...
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.
Server Monitoring: Uptime always in view
The permanent accessibility of your own server with fast response times is crucial for every commercial operator.
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 ...
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...
Port Monitoring: How to monitor the services on your servers
With port monitoring, you regularly check whether a specific network port is reachable and whether the service behind it...
Media Partner:
