dnsResCacheMaxTTL OBJECT-TYPE
SYNTAX DnsTime
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Maximum Time-To-Live for RRs in this cache. If the
resolver does not implement a TTL ceiling, the value of
this field should be zero."
View at oid-info.com
Maximum Time-To-Live for RRs in this cache. If the
resolver does not implement a TTL ceiling, the value of
this field should be zero.
Parsed from file rfc1612.mi2.txt
Company: None
Module: DNS-RESOLVER-MIB
Maximum Time-To-Live for RRs in this cache. If the
resolver does not implement a TTL ceiling, the value of
this field should be zero.
Parsed from file DNS-RESOLVER-MIB.mib
Module: DNS-RESOLVER-MIB
Automatically extracted from RFC1612
dnsResCacheMaxTTL OBJECT-TYPE SYNTAX DnsTime MAX-ACCESS read-write STATUS current DESCRIPTION "Maximum Time-To-Live for RRs in this cache. If the resolver does not implement a TTL ceiling, the value of this field should be zero." ::= { dnsResCache 2 }
dnsResCacheMaxTTL OBJECT-TYPE SYNTAX DnsTime MAX-ACCESS read-write STATUS current DESCRIPTION "Maximum Time-To-Live for RRs in this cache. If the resolver does not implement a TTL ceiling, the value of this field should be zero." ::= { dnsResCache 2 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.32.2.1.4.2.0 | dnsResCacheMaxTTL | 0 | 0 | None |
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.32.2.1.4.1 | dnsResCacheStatus | 1 | 1 | Status/action for the resolver's cache. enabled(1) means that the use of the cache is allowed. Query operations can return this s… |
1.3.6.1.2.1.32.2.1.4.3 | dnsResCacheGoodCaches | 1 | 1 | Number of RRs the resolver has cached successfully. |
1.3.6.1.2.1.32.2.1.4.4 | dnsResCacheBadCaches | 1 | 1 | Number of RRs the resolver has refused to cache because they appear to be dangerous or irrelevant. E.g., RRs with suspiciously h… |
1.3.6.1.2.1.32.2.1.4.5 | dnsResCacheRRTable | 1 | 11 | This table contains information about all the resource records currently in the resolver's cache. |