DNS query returned a name error. One or more FQDNs cannot be resolved.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Affirmed Networks MIB copies (Observium Community)
OID reference
1.3.6.1.4.1.37963.7.3.1.12
DNS query returned a name error. One or more FQDNs cannot be resolved.
Identification
{1 3 6 1 4 1 37963 7 3 1 12}
The displayed source records contain one distinct definition. Compare its source records.
anSsfAlarmDnsNameError NOTIFICATION-TYPE
OBJECTS {
affirmedSsfAlarmSeqId,
affirmedSsfAlarmDateTime,
affirmedSsfAlarmResource,
affirmedSsfAlarmSeverity,
affirmedSsfAlarmDetails
}
STATUS current
DESCRIPTION
"DNS query returned a name error. One or more FQDNs cannot be resolved."
-- IMPACT
-- "Session activations related to the specific FQDN will fail. This applies
-- to all 4 record types: A, AAAA, SRV, and NAPTR, and applies to any of up
-- to 8 configured servers. Negative responses from a DNS server can result
-- in negative caching as defined by RFC 2308. The retention time of these
-- entries is defined by the minimum of the TTL from the server and the locally
-- configured dns dns-if negative-cache-ttl. This alarm also covers the case
-- where all query results were eliminated by the configured dns-if exclude-label,
-- and the details string of the alarm tags it with [exclude-label]."
--
-- REPAIR-ACTION
-- "Update configuration on the DNS server or the SSF dns static-cache to
-- include the missing records as listed in the details portion of the alarm.
-- An unresolved name entry will be removed from the alarm immediately after
-- static-cache addition or when its negative cache TTL expires and another
-- query is triggered for that name and it is successful. A manual flush of
-- the dynamic-cache will also clear negative entries and hence the alarm.
-- Name errors due to exclude-label configuration can be resolved by updating the
-- static-cache, the DNS server, or the exclude-label. In the case of the latter
-- option, a manual action is required to clear the alarm entry, dynamic-cache flush."
::= { affirmedSsfTraps 12}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
DNS query returned a name error. One or more FQDNs cannot be resolved.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Affirmed Networks MIB copies (Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: anSsfAlarmDnsNameError
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"anSsfAlarmDnsNameError",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"affirmedSsfAlarmSeqId",
",",
"affirmedSsfAlarmDateTime",
",",
"affirmedSsfAlarmResource",
",",
"affirmedSsfAlarmSeverity",
",",
"affirmedSsfAlarmDetails",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"DNS query returned a name error. One or more FQDNs cannot be resolved.\"",
"::=",
"{",
"affirmedSsfTraps",
"12",
"}"
],
"syntax_tree": [
[
"Objects",
[
"affirmedSsfAlarmSeqId",
"affirmedSsfAlarmDateTime",
"affirmedSsfAlarmResource",
"affirmedSsfAlarmSeverity",
"affirmedSsfAlarmDetails"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"DNS query returned a name error. One or more FQDNs cannot be resolved."
],
null
]
}Vendor MIB copy from the Observium Community archive. Affirmed Networks support.
Module: AFFIRMED-SSF-MIB
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'enterprises', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'ITU-ALARM-TC-MIB': ['ItuPerceivedSeverity']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: AFFIRMED-SSF-MIB
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'enterprises', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'ITU-ALARM-TC-MIB': ['ItuPerceivedSeverity']}Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.37963.7.3.1.1 | anSsfAlarmDnsServiceReachability | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.2 | anSsfAlarmGtpPathStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.3 | anSsfAlarmLdapPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.4 | anSsfAlarmNetworkKeepaliveStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.5 | anSsfAlarmLdapDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.6 | anSsfAlarmOperState | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.7 | anSsfAlarmRestPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.8 | anSsfAlarmRestDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.9 | anSsfAlarmPgwGxMapping | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.10 | anSsfAlarmDiameterPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.11 | anSsfAlarmDiameterDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.13 | anSsfAlarmConfigSync | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.14 | anSsfAlarmLoginFailure | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.15 | anSsfAlarmFileSystem | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.16 | anSsfAlarmCpu | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.17 | anSsfAlarmMemory | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.18 | anSsfAlarmNetworkNextHopStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.19 | anSsfAlarmNetworkStaticRouteStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.20 | anSsfAlarmStatusSync | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.21 | anSsfAlarmGatewaySnmpStatus | 0 | 0 |