dnsResConfigImplementIdent |
.1.3.6.1.2.1.32.2.1.1.1 |
The implementation identification string for the
resolver software in use on the system, for example;
`RES-2.1'
|
dnsResConfigService |
.1.3.6.1.2.1.32.2.1.1.2 |
Kind of DNS resolution service provided:
recursiveOnly(1) indicates a stub resolver.
iterativeOnly(2) indicates a normal full service
resolver.
recursiveAndIterative(3) indicates a full-service
resolver which performs a mix of recursive and iterative
queries.
|
dnsResConfigMaxCnames |
.1.3.6.1.2.1.32.2.1.1.3 |
Limit on how many CNAMEs the resolver should allow
before deciding that there's a CNAME loop. Zero means
that resolver has no explicit CNAME limit.
|
dnsResConfigSbeltEntry |
.1.3.6.1.2.1.32.2.1.1.4.1 |
An entry in the resolver's Sbelt table.
Rows may be created or deleted at any time by the DNS
resolver and by SNMP SET requests. Whether the values
changed via SNMP are saved in stable storage across
`reset' operations is implementation-specific.
|
dnsResConfigUpTime |
.1.3.6.1.2.1.32.2.1.1.5 |
If the resolver has a persistent state (e.g., a
process), this value will be the time elapsed since it
started. For software without persistant state, this
value will be 0.
|
dnsResConfigResetTime |
.1.3.6.1.2.1.32.2.1.1.6 |
If the resolver has a persistent state (e.g., a process)
and supports a `reset' operation (e.g., can be told to
re-read configuration files), this value will be the
time elapsed since the last time the resolver was
`reset.' For software that does not have persistence or
does not support a `reset' operation, this value will be
zero.
|
dnsResConfigReset |
.1.3.6.1.2.1.32.2.1.1.7 |
Status/action object to reinitialize any persistant
resolver state. When set to reset(2), any persistant
resolver state (such as a process) is reinitialized as if
the resolver had just been started. This value will
never be returned by a read operation. When read, one of
the following values will be returned:
other(1) - resolver in some unknown state;
initializing(3) - resolver (re)initializing;
running(4) - resolver currently running.
|
dnsResCounterByOpcodeEntry |
.1.3.6.1.2.1.32.2.1.2.3.1 |
Entry in the resolver counter table. Entries are
indexed by DNS OpCode.
|
dnsResCounterByRcodeEntry |
.1.3.6.1.2.1.32.2.1.2.4.1 |
Entry in the resolver response table. Entries are
indexed by DNS response code.
|
dnsResCounterNonAuthDataResps |
.1.3.6.1.2.1.32.2.1.2.5 |
Number of requests made by the resolver for which a
non-authoritative answer (cached data) was received.
|
dnsResCounterNonAuthNoDataResps |
.1.3.6.1.2.1.32.2.1.2.6 |
Number of requests made by the resolver for which a
non-authoritative answer - no such data response (empty
answer) was received.
|
dnsResCounterMartians |
.1.3.6.1.2.1.32.2.1.2.7 |
Number of responses received which were received from
servers that the resolver does not think it asked.
|
dnsResCounterRecdResponses |
.1.3.6.1.2.1.32.2.1.2.8 |
Number of responses received to all queries.
|
dnsResCounterUnparseResps |
.1.3.6.1.2.1.32.2.1.2.9 |
Number of responses received which were unparseable.
|
dnsResCounterFallbacks |
.1.3.6.1.2.1.32.2.1.2.10 |
Number of times the resolver had to fall back to its
seat belt information.
|
dnsResLameDelegationOverflows |
.1.3.6.1.2.1.32.2.1.3.1 |
Number of times the resolver attempted to add an entry
to the Lame Delegation table but was unable to for some
reason such as space constraints.
|
dnsResLameDelegationEntry |
.1.3.6.1.2.1.32.2.1.3.2.1 |
Entry in lame delegation table. Only the resolver may
create rows in this table. SNMP SET requests may be used
to delete rows.
|
dnsResCacheStatus |
.1.3.6.1.2.1.32.2.1.4.1 |
Status/action for the resolver's cache.
enabled(1) means that the use of the cache is allowed.
Query operations can return this state.
disabled(2) means that the cache is not being used.
Query operations can return this state.
Setting this variable to clear(3) deletes the entire
contents of the resolver's cache, but does not otherwise
change the resolver's state. The status will retain its
previous value from before the clear operation (i.e.,
enabled(1) or disabled(2)). The value of clear(3) can
NOT be returned by a query operation.
|
dnsResCacheMaxTTL |
.1.3.6.1.2.1.32.2.1.4.2 |
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.
|
dnsResCacheGoodCaches |
.1.3.6.1.2.1.32.2.1.4.3 |
Number of RRs the resolver has cached successfully.
|
dnsResCacheBadCaches |
.1.3.6.1.2.1.32.2.1.4.4 |
Number of RRs the resolver has refused to cache because
they appear to be dangerous or irrelevant. E.g., RRs
with suspiciously high TTLs, unsolicited root
information, or that just don't appear to be relevant to
the question the resolver asked.
|
dnsResCacheRREntry |
.1.3.6.1.2.1.32.2.1.4.5.1 |
An entry in the resolvers's cache. Rows may be created
only by the resolver. SNMP SET requests may be used to
delete rows.
|
dnsResNCacheStatus |
.1.3.6.1.2.1.32.2.1.5.1 |
Status/action for the resolver's negative response
cache.
enabled(1) means that the use of the negative response
cache is allowed. Query operations can return this
state.
disabled(2) means that the negative response cache is
not being used. Query operations can return this state.
Setting this variable to clear(3) deletes the entire
contents of the resolver's negative response cache. The
status will retain its previous value from before the
clear operation (i.e., enabled(1) or disabled(2)). The
value of clear(3) can NOT be returned by a query
operation.
|
dnsResNCacheMaxTTL |
.1.3.6.1.2.1.32.2.1.5.2 |
Maximum Time-To-Live for cached authoritative errors.
If the resolver does not implement a TTL ceiling, the
value of this field should be zero.
|
dnsResNCacheGoodNCaches |
.1.3.6.1.2.1.32.2.1.5.3 |
Number of authoritative errors the resolver has cached
successfully.
|
dnsResNCacheBadNCaches |
.1.3.6.1.2.1.32.2.1.5.4 |
Number of authoritative errors the resolver would have
liked to cache but was unable to because the appropriate
SOA RR was not supplied or looked suspicious.
|
dnsResNCacheErrEntry |
.1.3.6.1.2.1.32.2.1.5.5.1 |
An entry in the resolver's negative response cache
table. Only the resolver can create rows. SNMP SET
requests may be used to delete rows.
|
dnsResOptCounterReferals |
.1.3.6.1.2.1.32.2.1.6.1 |
Number of responses which were received from servers
redirecting query to another server.
|
dnsResOptCounterRetrans |
.1.3.6.1.2.1.32.2.1.6.2 |
Number requests retransmitted for all reasons.
|
dnsResOptCounterNoResponses |
.1.3.6.1.2.1.32.2.1.6.3 |
Number of queries that were retransmitted because of no
response.
|
dnsResOptCounterRootRetrans |
.1.3.6.1.2.1.32.2.1.6.4 |
Number of queries that were retransmitted that were to
root servers.
|
dnsResOptCounterInternals |
.1.3.6.1.2.1.32.2.1.6.5 |
Number of requests internally generated by the
resolver.
|
dnsResOptCounterInternalTimeOuts |
.1.3.6.1.2.1.32.2.1.6.6 |
Number of requests internally generated which timed
out.
|
dnsResConfigSbeltAddr |
.1.3.6.1.2.1.32.2.1.1.4.1.1 |
The IP address of the Sbelt name server identified by
this row of the table.
|
dnsResConfigSbeltSubTree |
.1.3.6.1.2.1.32.2.1.1.4.1.5 |
Queries sent to the name server identified by this row
of the table are limited to those for names in the name
subtree identified by this variable. If no such
limitation applies, the value of this variable is the
name of the root domain (a DNS name consisting of a
single zero octet).
|
dnsResConfigSbeltClass |
.1.3.6.1.2.1.32.2.1.1.4.1.6 |
The class of DNS queries that will be sent to the server
identified by this row of the table.
|
dnsResConfigSbeltName |
.1.3.6.1.2.1.32.2.1.1.4.1.2 |
The DNS name of a Sbelt nameserver identified by this
row of the table. A zero-length string indicates that
the name is not known by the resolver.
|
dnsResConfigSbeltRecursion |
.1.3.6.1.2.1.32.2.1.1.4.1.3 |
Kind of queries resolver will be sending to the name
server identified in this row of the table:
iterative(1) indicates that resolver will be directing
iterative queries to this name server (RD bit turned
off).
recursive(2) indicates that resolver will be directing
recursive queries to this name server (RD bit turned
on).
recursiveAndIterative(3) indicates that the resolver
will be directing both recursive and iterative queries
to the server identified in this row of the table.
|
dnsResConfigSbeltPref |
.1.3.6.1.2.1.32.2.1.1.4.1.4 |
This value identifies the preference for the name server
identified in this row of the table. The lower the
value, the more desirable the resolver considers this
server.
|
dnsResConfigSbeltStatus |
.1.3.6.1.2.1.32.2.1.1.4.1.7 |
Row status column for this row of the Sbelt table.
|
dnsResCounterByOpcodeCode |
.1.3.6.1.2.1.32.2.1.2.3.1.1 |
The index to this table. The OpCodes that have already
been defined are found in RFC-1035.
|
dnsResCounterByOpcodeQueries |
.1.3.6.1.2.1.32.2.1.2.3.1.2 |
Total number of queries that have sent out by the
resolver since initialization for the OpCode which is
the index to this row of the table.
|
dnsResCounterByOpcodeResponses |
.1.3.6.1.2.1.32.2.1.2.3.1.3 |
Total number of responses that have been received by the
resolver since initialization for the OpCode which is
the index to this row of the table.
|
dnsResCounterByRcodeCode |
.1.3.6.1.2.1.32.2.1.2.4.1.1 |
The index to this table. The Response Codes that have
already been defined are found in RFC-1035.
|
dnsResCounterByRcodeResponses |
.1.3.6.1.2.1.32.2.1.2.4.1.2 |
Number of responses the resolver has received for the
response code value which identifies this row of the
table.
|
dnsResLameDelegationSource |
.1.3.6.1.2.1.32.2.1.3.2.1.1 |
Source of lame delegation.
|
dnsResLameDelegationName |
.1.3.6.1.2.1.32.2.1.3.2.1.2 |
DNS name for which lame delegation was received.
|
dnsResLameDelegationClass |
.1.3.6.1.2.1.32.2.1.3.2.1.3 |
DNS class of received lame delegation.
|
dnsResLameDelegationCounts |
.1.3.6.1.2.1.32.2.1.3.2.1.4 |
How many times this lame delegation has been received.
|
dnsResLameDelegationStatus |
.1.3.6.1.2.1.32.2.1.3.2.1.5 |
Status column for the lame delegation table. Since only
the agent (DNS resolver) creates rows in this table, the
only values that a manager may write to this variable
are active(1) and destroy(6).
|
dnsResCacheRRName |
.1.3.6.1.2.1.32.2.1.4.5.1.1 |
Owner name of the Resource Record in the cache which is
identified in this row of the table. As described in
RFC-1034, the owner of the record is the domain name
were the RR is found.
|
dnsResCacheRRClass |
.1.3.6.1.2.1.32.2.1.4.5.1.2 |
DNS class of the Resource Record in the cache which is
identified in this row of the table.
|
dnsResCacheRRType |
.1.3.6.1.2.1.32.2.1.4.5.1.3 |
DNS type of the Resource Record in the cache which is
identified in this row of the table.
|
dnsResCacheRRIndex |
.1.3.6.1.2.1.32.2.1.4.5.1.9 |
A value which makes entries in the table unique when the
other index values (dnsResCacheRRName,
dnsResCacheRRClass, and dnsResCacheRRType) do not
provide a unique index.
|
dnsResCacheRRTTL |
.1.3.6.1.2.1.32.2.1.4.5.1.4 |
Time-To-Live of RR in DNS cache. This is the initial
TTL value which was received with the RR when it was
originally received.
|
dnsResCacheRRElapsedTTL |
.1.3.6.1.2.1.32.2.1.4.5.1.5 |
Elapsed seconds since RR was received.
|
dnsResCacheRRSource |
.1.3.6.1.2.1.32.2.1.4.5.1.6 |
Host from which RR was received, 0.0.0.0 if unknown.
|
dnsResCacheRRData |
.1.3.6.1.2.1.32.2.1.4.5.1.7 |
RDATA portion of a cached RR. The value is in the
format defined for the particular DNS class and type of
the resource record.
|
dnsResCacheRRStatus |
.1.3.6.1.2.1.32.2.1.4.5.1.8 |
Status column for the resolver cache table. Since only
the agent (DNS resolver) creates rows in this table, the
only values that a manager may write to this variable
are active(1) and destroy(6).
|
dnsResCacheRRPrettyName |
.1.3.6.1.2.1.32.2.1.4.5.1.10 |
Name of the RR at this row in the table. This is
identical to the dnsResCacheRRName variable, except that
character case is preserved in this variable, per DNS
conventions.
|
dnsResNCacheErrQName |
.1.3.6.1.2.1.32.2.1.5.5.1.1 |
QNAME associated with a cached authoritative error.
|
dnsResNCacheErrQClass |
.1.3.6.1.2.1.32.2.1.5.5.1.2 |
DNS QCLASS associated with a cached authoritative
error.
|
dnsResNCacheErrQType |
.1.3.6.1.2.1.32.2.1.5.5.1.3 |
DNS QTYPE associated with a cached authoritative error.
|
dnsResNCacheErrIndex |
.1.3.6.1.2.1.32.2.1.5.5.1.9 |
A value which makes entries in the table unique when the
other index values (dnsResNCacheErrQName,
dnsResNCacheErrQClass, and dnsResNCacheErrQType) do not
provide a unique index.
|
dnsResNCacheErrTTL |
.1.3.6.1.2.1.32.2.1.5.5.1.4 |
Time-To-Live of a cached authoritative error at the time
of the error, it should not be decremented by the number
of seconds since it was received. This should be the
TTL as copied from the MINIMUM field of the SOA that
accompanied the authoritative error, or a smaller value
if the resolver implements a ceiling on negative
response cache TTLs.
|
dnsResNCacheErrElapsedTTL |
.1.3.6.1.2.1.32.2.1.5.5.1.5 |
Elapsed seconds since authoritative error was received.
|
dnsResNCacheErrSource |
.1.3.6.1.2.1.32.2.1.5.5.1.6 |
Host which sent the authoritative error, 0.0.0.0 if
unknown.
|
dnsResNCacheErrCode |
.1.3.6.1.2.1.32.2.1.5.5.1.7 |
The authoritative error that has been cached:
nonexistantName(1) indicates an authoritative name error
(RCODE = 3).
noData(2) indicates an authoritative response with no
error (RCODE = 0) and no relevant data.
other(3) indicates some other cached authoritative
error. At present, no such errors are known to exist.
|
dnsResNCacheErrStatus |
.1.3.6.1.2.1.32.2.1.5.5.1.8 |
Status column for the resolver negative response cache
table. Since only the agent (DNS resolver) creates rows
in this table, the only values that a manager may write
to this variable are active(1) and destroy(6).
|
dnsResNCacheErrPrettyName |
.1.3.6.1.2.1.32.2.1.5.5.1.10 |
QNAME associated with this row in the table. This is
identical to the dnsResNCacheErrQName variable, except
that character case is preserved in this variable, per
DNS conventions.
|