Dns monitor

Windows DNS ServerThis template assesses the status and overall health of services and performance of a Microsoft DNS server.Prerequisites: WMI access to the target server.Credentials: Windows Administrator on the target server.Monitored ComponentsNote: You need to set thresholds for counters according to your environment. It is recommended to monitor counters for some length of time to understand potential value ranges and then set the thresholds accordingly. For more information, see DNS ServerThis component monitor enables DNS clients to resolve DNS names by answering DNS queries and dynamic DNS update requests. If this service is stopped or disabled, DNS updates will not occur and any services that explicitly depend on it will fail to start.Memory: Caching MemoryThis component monitor returns the total amount of system memory in use by the DNS Server service for caching.Monitor this counter to determine whether cache use is optimizing the use of available memory.Memory: Database Node MemoryThis component monitor returns the total amount of system memory in use by the DNS Server service for database nodes.Memory: Nbstat MemoryThis component monitor returns the total amount of system memory in use by the DNS Server service for Nbtstat.Memory: Record Flow MemoryThis component monitor returns the total amount of system memory in use by the DNS Server service for record flow.Dynamic Update: NoOperation/secThis component monitor returns the average number of No-operation/Empty dynamic update requests received by the DNS server per second.Dynamic Update: ReceivedThis component monitor returns the total number of dynamic update requests received by the DNS server.Monitor this counter after enabling dynamic updates to determine whether DNS clients are attempting to update their DNS addresses.Dynamic Update: RejectedThis component monitor returns the total number of dynamic updates rejected by the DNS server.Monitor this counter and compare this value against Dynamic Update: Received to determine how many systems are experiencing problems updating DNS addresses.Dynamic Update: TimeOutsThis component monitor returns the total number of dynamic update time-outs of the DNS server.Dynamic Update: Written to DatabaseThis component monitor returns the total number of dynamic updates written to the database by the DNS server.Monitor this counter and compare this value against Dynamic Update: Received to determine how many systems are successfully updating DNS records.Recursive: Queries/secThis component monitor returns the average number of recursive queries received by the DNS server per second.Recursive: Query Failure/secThis component monitor returns the average number of recursive query failures per second.Recursive: TimeOut/secThis component monitor returns the average number of recursive

Query sending time-outs per second.Secure Update: FailureThis component monitor returns the total number of secure updates that failed on the DNS server.Monitor this counter to determine whether or not clients can perform secure dynamic updates. Also, compare this value against Secure Update: Received to determine how many systems fail to perform secure updates in DNS.Secure Update: ReceivedThis component monitor returns the total number of secure update requests received by the DNS server.Monitor this counter and compare this value against Secure Update: Failure to determine how many systems are successfully performing secure updates in DNS.TCP: Message MemoryThis component monitor returns the total amount of TCP message memory used by the DNS server.TCP: Query Received/secThis component monitor returns the average number of TCP queries received by the DNS server per second.TCP: Response Sent/secThis component monitor returns the average number of TCP responses sent by the DNS server per second.Total Query Received/secThis component monitor returns the average number of queries received by the DNS server per second.Monitor this counter to create baselines of server usage in heavily trafficked networks.Total Response Sent/secThis component monitor returns the average number of responses sent by the DNS server per second.Monitor this counter to create baselines of server usage in heavily trafficked networks.UDP: Message MemoryThis component monitor returns the total amount of UDP message memory used by the DNS server.UDP: Query Received/secThis component monitor returns the average number of UDP queries received by the DNS server per second.UDP: Response Sent/secThis component monitor returns the average number of UDP responses sent by the DNS server per second.Zone Transfer: FailureThis component monitor returns the total number of failed zone transfers of the master DNS server.Monitor this counter to troubleshoot name resolution failures.Zone Transfer: SuccessThis component monitor returns the total number of successful zone transfers of the master DNS server.Monitor this counter to troubleshoot name resolution failures.DNS User Experience MonitorThis component monitor tests a DNS server's ability to respond to a record query, compares the query response against a list of IP addresses, and measures the response time. The component monitor passes if the DNS response matches the expected IP addresses.Portions of this document were originally created by and are excerpted from the following sources: Pauli Pesonen, “Microsoft Exchange Server 2003 Installation and the Management,” Copyright 2007-2012 Pauli Pesonen. All rights reserved. Available at

This monitor tests the availability of the DNS service on remote IP interfaces.A DNS query is sent to check for a response of either an A or AAAA resource record.The monitor is marked as up if it receives a valid response from the DNS Server.For hostnames that have multiple resource records, it is possible to test if the number of responses are within a given boundary.The monitor can be simulated with the command line tool host:~ % host -v -t a www.google.com 8.8.8.8Trying "www.google.com"Using domain server:Name: 8.8.8.8Address: 8.8.8.8#53Aliases:;; ->>HEADERThis monitor is intended for testing the availability of a DNS service.To monitor the DNS resolution of some of your nodes from a client’s perspective, use the DNSResolutionMonitor.DnsMonitor versus DNSResolutionMonitorThe DnsMonitor is a test against a specific DNS server.Use this service to determine if the monitored node provides DNS resolution of requests sent to it.In Horizon, the DNS server is the node and the DnsMonitor sends a lookup request for a given A record to the DNS server IP address.The service goes down if the DNS server doesn’t have a valid A record in its zone database or has other issues resolving A records.The DNSResolutionMonitor measures the availability and record outages of hostname resolution from a client perspective.Use this service to determine if the monitored node can be resolved by DNS hosted somewhere else in your network.Monitor factsClass Nameorg.opennms.netmgt.poller.monitors.DnsMonitorConfiguration and useTable 1. Optional monitor-specific parameters for the DnsMonitorParameterDescriptionDefaultretryNumber of retries before the service is marked as down.0timeoutTime in milliseconds to wait for the A Record response from the server.5000portUDP port for the DNS server53lookupDNS A Record for lookup testlocalhostfatal-response-codesA comma-separated list of numeric DNS response codes considered fatal if present in the server’s response.Default value is 2 and corresponds to Server Failed.See RFC 2929 for a list of codes and their meanings.2min-answersMinimum number of records in the DNS server response for the given lookup.n/amax-answersMaximum number of records in the DNS server response for the given lookup.n/aExampleThis example shows how to monitor whether the IP interface from a given DNS server resolves a DNS request.This service should be bound to a DNS server which should be able to give a valid DNS response for a request to www.google.com.The service is up if the DNS server gives between one and ten A record responses.Note that you must include the monitor section for each service in your definition.Example configuration monitoring DNS request for a given server for www.google.com To have response time graphs for the name resolution, you must configure RRD graphs for the given ds-names (dns-res-v4, dns-res-v6, dns-res-both, dns-res-either, dns-res-cname-mx) in ${OPENNMS_HOME}/etc/response-graph.properties.

DNS is a pivotal service when you host a website online. Though Google Cloud DNS is an established, reliable cloud DNS provider, use Site24x7's monitoring capabilities to know its latency and DNS response counts.Setup and configurationAdding Google Cloud DNS while configuring a new Google Cloud monitor If you have not configured a Google Cloud monitor yet, add one by following the steps below:Log in to your Site24x7 account.Go to Cloud > GCP > Add GCP Monitor or Admin > Cloud Monitoring > Google Cloud Platform(GCP).Provide a unique display name for identification purposes.Upload a service account JSON file to authenticate Site24x7 for performing resource discovery.Select Cloud DNS from the Select the Resources for Monitoring list.Select existing Notification Profiles, User Alerts Groups, Tags, and IT Automation Templates or add new ones. You can also integrate Site24x7's alarms with your preferred third-party service.Click Start GCP Monitoring.Adding Google Cloud DNS to an existing Google Cloud monitor If you already have a Google Cloud monitor configured for the service account, you can add Google Cloud DNS by following the steps below:Log in to your Site24x7 account.Go to Cloud > GCP and select your GCP monitor.Click the hamburger icon next to Service View and select Edit, which brings you to the Edit GCP Monitor page.On the Edit GCP Monitor page, select Cloud DNS from the Select the Resources for Monitoring list and click Save.After successful configuration, go to Cloud > GCP > Cloud DNS. Now you can view the discovered Cloud DNS resources.NoteIt will take approximately