dnsResCacheRRTable OBJECT-TYPE
SYNTAX SEQUENCE OF DnsResCacheRREntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about all the resource
records currently in the resolvers cache."
View at oid-info.com
This table contains information about all the resource
records currently in the resolver's cache.
Parsed from file rfc1612.mi2.txt
Company: None
Module: DNS-RESOLVER-MIB
This table contains information about all the resource
records currently in the resolver's cache.
Parsed from file DNS-RESOLVER-MIB.mib
Module: DNS-RESOLVER-MIB
Automatically extracted from RFC1612
dnsResCacheRRTable OBJECT-TYPE SYNTAX SEQUENCE OF DnsResCacheRREntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about all the resource records currently in the resolver's cache." ::= { dnsResCache 5 }
dnsResCacheRRTable OBJECT-TYPE SYNTAX SEQUENCE OF DnsResCacheRREntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about all the resource records currently in the resolver's cache." ::= { dnsResCache 5 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.32.2.1.4.5.1 | dnsResCacheRREntry | 10 | 10 | An entry in the resolvers's cache. Rows may be created only by the resolver. SNMP SET requests may be used to delete rows. |
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.2 | dnsResCacheMaxTTL | 1 | 1 | 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 … |
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… |