OID reference

dnsResConfigMaxCnames

1.3.6.1.2.1.32.2.1.1.3

Description

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.

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.2.1.32.2.1.1 (dnsResConfig)
Node code
3
Node name
dnsResConfigMaxCnames
Category
SNMP management object
Numeric OID
1.3.6.1.2.1.32.2.1.1.3
URN notation
urn:oid:1.3.6.1.2.1.32.2.1.1.3
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 2 1 32 2 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) dns(32) dnsResMIB(2) dnsResMIBObjects(1) dnsResConfig(1) dnsResConfigMaxCnames(3)}
OID-IRI notation
  • /1/3/6/1/2/1/32/2/1/1/3
  • /ISO/Identified-Organization/6/1/2/1/32/2/1/1/3
  • /ISO/3/6/1/2/1/32/2/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/identified-organization/dod/internet/mgmt/mib/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/org/dod/internet/mgmt/mib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/org/dod/internet/mgmt/mib/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/org/dod/internet/mgmt/stdmib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-identified-organization/dod/internet/mgmt/stdmib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-organization/dod/internet/mgmt/mib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-organization/dod/internet/mgmt/mib/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames
  • /iso/iso-organization/dod/internet/mgmt/stdmib-2/dns/dnsResMIB/dnsResMIBObjects/dnsResConfig/dnsResConfigMaxCnames

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-only, read-write
Status in MIB
current

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — LANCOM official release MIBs, NETGEAR official product and EOL MIB downloads

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current
Allowed ranges
0–2147483647

Variant 2 — MIBdepot, Circitor

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Allowed ranges
0–2147483647

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.2.1.32.2.1.1.3.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

dnsResConfigMaxCnames · current

dnsResConfigMaxCnames OBJECT-TYPE
       SYNTAX      INTEGER (0..2147483647)
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
               "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."
       REFERENCE
               "RFC-1035 section 7.1."
       ::= { dnsResConfig 3 }

dnsResConfigMaxCnames · current

dnsResConfigMaxCnames OBJECT-TYPE
       SYNTAX      INTEGER (0..2147483647)
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
               "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."
       REFERENCE
               "RFC-1035 section 7.1."
       ::= { dnsResConfig 3 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

Limit on how many CNAMEs the resolver should allow before deciding that theres a CNAME loop. Zero means that resolver has no explicit CNAME limit.
Original text from OID Repository
dnsResConfigMaxCnames OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Limit on how many CNAMEs the resolver should allow
before deciding that theres a CNAME loop. Zero means
that resolver has no explicit CNAME limit."
REFERENCE
"RFC-1035 section 7.1."
Sources for this description

OID Repository

View at oid-base.com
Automatically extracted from RFC1612

Description 2

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.
Sources for this description

LANCOM official release MIBsNETGEAR official product and EOL MIB downloads

See 1 matching source record

Circitor

Parsed from DNS-RESOLVER-MIB.mib · DNS-RESOLVER-MIB

Source file: Download RFC 1612 · Publisher's file · RFC errata

Source file: Download stddns.mib · Publisher's file

Source file: Download rfc1612.mib · Publisher's file

Evidence

Source records

1 records

Matching descriptions are grouped; representative source files are shown for each definition.

Records for description 2LANCOM official release MIBs, NETGEAR official product and EOL MIB downloads1 record · 5 sources

Description 2

dnsResConfigMaxCnames · currentLANCOM official release MIBs, NETGEAR official product and EOL MIB downloads5 sources

Status in source: current.

Names: dnsResConfigMaxCnames

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dnsResConfigMaxCnames",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "2147483647",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"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.\"",
    "REFERENCE",
    "\"RFC-1035 section 7.1.\"",
    "::=",
    "{",
    "dnsResConfig",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            2147483647
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "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."
    ],
    [
      "REFERENCE",
      "RFC-1035 section 7.1."
    ],
    null,
    null,
    null
  ]
}

Historical records

Additional source information

Information from MIBdepot
dnsResConfigMaxCnames OBJECT-TYPE
       SYNTAX      INTEGER (0..2147483647)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
               "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."
       REFERENCE
               "RFC-1035 section 7.1."
       ::= { dnsResConfig 3 }
Information from Circitor
dnsResConfigMaxCnames OBJECT-TYPE
       SYNTAX      INTEGER (0..2147483647)
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
               "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."
       REFERENCE
               "RFC-1035 section 7.1."
       ::= { dnsResConfig 3 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.32.2.1.1.3.0 dnsResConfigMaxCnames00

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.32.2.1.1.1 dnsResConfigImplementIdent11 The implementation identification string for the
resolver software in use on the system, for example;
`RES-2.1'
1.3.6.1.2.1.32.2.1.1.2 dnsResConfigService11 Kind of DNS resolution service provided:

recursiveOnly(1) indicates a stub resolver.

iterativeOnly(2) indicates a normal full ser…
1.3.6.1.2.1.32.2.1.1.4 dnsResConfigSbeltTable18 Table of safety belt information used by the resolver
when it hasn't got any better idea of where to send a
query, such as when t…
1.3.6.1.2.1.32.2.1.1.5 dnsResConfigUpTime11 If the resolver has a persistent state (e.g., a
process), this value will be the time elapsed since it
started. For software wit…
1.3.6.1.2.1.32.2.1.1.6 dnsResConfigResetTime11 If the resolver has a persistent state (e.g., a process)
and supports a `reset' operation (e.g., can be told to
re-read configura…
1.3.6.1.2.1.32.2.1.1.7 dnsResConfigReset11 Status/action object to reinitialize any persistant
resolver state. When set to reset(2), any persistant
resolver state (such as…