TELDAT-MON-FEATURES-DNS-MIB

All MIBs › TELDAT-MON-FEATURES-DNS-MIB

Category: Teldat Router Management

Description: Monitors Teldat router DNS feature status, resolver cache statistics, and query performance counters.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TELDAT-MON-FEATURES-DNS-MIB?

TELDAT-MON-FEATURES-DNS-MIB is a Teldat proprietary monitoring MIB covering the status of the router's built-in DNS feature, including its resolver cache and query performance. It exposes service-status data - counters and state indicators for the DNS resolver/proxy function running on the router - rather than raw network-layer counters. This makes it a software-service health monitor: it lets an operator confirm the DNS feature itself is running correctly, tracking resolver cache utilization and query success/failure counts to detect problems such as an unreachable upstream DNS server, cache exhaustion, or elevated query latency, all of which manifest as end-user connectivity or name-resolution complaints even when the WAN link itself is healthy. It is a Teldat-specific extension used alongside the router's core DNS relay/proxy configuration rather than any external standards MIB. It is deployed on Teldat routers that provide local DNS caching/relay for branch-office LAN clients, where visibility into resolver health helps distinguish DNS problems from broader connectivity issues. Engineers can download the TELDAT-MON-FEATURES-DNS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-MON-FEATURES-DNS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Teldat router

Monitoring Examples

No sample object names were provided for this module, but its function corresponds to resolver cache size and query success/failure counters typical of Teldat's feature-monitoring modules. An administrator would poll the query failure counter and see it climb sharply when an upstream DNS server becomes unreachable, even while the WAN link itself stays up. Comparing cache statistics over time also helps confirm whether increased query volume is being effectively absorbed by local caching.

What Can Be Monitored

DNS resolver cache statistics
DNS query success/failure counters
DNS feature operational status

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1213-MIB

DisplayString

From TELDAT-SW-STRUCTURE-MIB

telProdNpMonFeatures

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
telProdNpMonFeatDNS	1.3.6.1.4.1.2007.4.1.2.4.8
teldatDNSMonProbeGroup	1.3.6.1.4.1.2007.4.1.2.4.8.1
teldatDNSMonProbeTable	1.3.6.1.4.1.2007.4.1.2.4.8.1.1		not-accessible	DNS probes table. Each entry identifies a DNS probe.
teldatDNSMonProbeEntry	1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1		not-accessible	An entry identifies a DNS probe, used to measure the DNS resolution time, and it is comprised of the following parameters: the probe identifier, the probe status, the URL used for the last resolve time measurement, the date and time that the probe was last started and the resolve time measured.
INT teldatDNSMonProbeIdentifier	1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.1	INTEGER	read-only	Index of the table: probe indentifier.
STR teldatDNSMonProbeStatus	1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.2	DisplayString	read-only	Status of the DNS probe: Waiting, executing, or completed correctly or with errors.
STR teldatDNSMonProbeURL	1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.3	DisplayString	read-only	First resolved URL for the given DNS probe.
OCT teldatDNSMonProbeInitDate	1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.4	OCTET STRING	read-only	The date the probe was last started. If the probe has not ever been started yet, this is shown as 0.
OCT teldatDNSMonProbeInitTime	1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.5	OCTET STRING	read-only	The time the probe was last started. If the probe has not ever been started yet, this is shown as 0.
INT teldatDNSMonProbeResolveTime	1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.6	INTEGER	read-only	Measured resolve time.
teldatDNSMonProbeStartTable	1.3.6.1.4.1.2007.4.1.2.4.8.1.2		not-accessible	This table allows to start the execution of the probe whose identifier takes the value given by the index. Each entry refers to one of the configured probes, and consists of two variables: the identifier of the probe, which is the index of the table, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
teldatDNSMonProbeStartEntry	1.3.6.1.4.1.2007.4.1.2.4.8.1.2.1		not-accessible	Each entry refers to one of the configured probes, and consists of two variables: the identifier of the probe, which is the index of the table, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
INT teldatDNSMonProbeStartIndex	1.3.6.1.4.1.2007.4.1.2.4.8.1.2.1.1	INTEGER	read-only	Index of the table: probe identifier.
INT teldatDNSMonProbeStartCommand	1.3.6.1.4.1.2007.4.1.2.4.8.1.2.1.2	INTEGER	read-write	If the value of this variable is set to 1, the execution of the probe whose identifier takes the value given by the index will start. In GET operations, the value taken by this variable indicates the result of the last operation: ok (2), if the last operation was made succesfully; the value undefined (3) indicates that operations of this type have not been made yet. If the operation failed, this variable could take different values depending on the error cause: no-memory (4), if there was not enough memory to start the DNS probe; wrong-identifier(5) if the probe identifier introduced was not correct; already-started (6) indicates that the probe which was going to be started was started previously and is in execution; dns-uninitialized (7) if the DNS system has not been initialized; error (8) if another generic error has occurred.
teldatDNSMonProbeResetPPPAndStartTable	1.3.6.1.4.1.2007.4.1.2.4.8.1.3		not-accessible	This table allows to start the execution of the probe whose identifier takes the value given by the index once the PPP indicated has restablished connection after being shut down. Each entry refers to a pair probe-ppp connection, and consists of three variables: the identifier of the probe, the identifier of the PPP interface, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
teldatDNSMonProbeResetPPPAndStartEntry	1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1		not-accessible	Each entry refers to a pair probe-ppp connection, and consists of three variables: the identifier of the probe, the identifier of the PPP interface, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
INT teldatDNSMonProbeResetPPPAndStartIndex	1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1.1	INTEGER	read-only	Index of the table: probe identifier.
INT teldatDNSMonProbeResetPPPIndex	1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1.2	INTEGER	read-only	Index of the table: number of the PPP interface.
INT teldatDNSMonProbeResetPPPAndStartCommand	1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1.3	INTEGER	read-write	If the value of this variable is set to 1, the PPP connection established through the interface given by the index will be disconnect and the DNS probe given by the other index will be started once the PPP connection restablishes. In GET operations, the value taken by this variable indicates the result of the last operation: ok (2), if the last operation was made succesfully; the value undefined (3) indicates that operations of this type have not been made yet. If the operation failed, this variable could take different values depending on the error cause: no-memory (4), if there was not enough memory to start the DNS probe; wrong-identifier(5) if the probe identifier introduced was not correct; already-started (6) indicates that the probe which was going to be started was started previously and is in execution; dns-uninitialized (7) if the DNS system has not been initialized; error (8) if another generic error has occurred.

RFC description

Teldat vendor-private MIB for monitoring DNS features and operations on Teldat equipment.

Start monitoring Teldat router (DNS resolver/cache service status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TELDAT-MON-FEATURES-DNS-MIB

What Is TELDAT-MON-FEATURES-DNS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description