AT-DNS-CLIENT-MIB

All MIBs › AT-DNS-CLIENT-MIB

Organization: Allied Telesis, Inc

Last Updated: 2010-06-14

Category: IP and Core Protocols, Vendor: Allied Telesis

Description: Manages DNS client resolver configuration including server addresses and domain search lists on Allied Telesis devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is AT-DNS-CLIENT-MIB?

AT-DNS-CLIENT-MIB is a vendor-specific MIB from Allied Telesis defining managed objects for the DNS client resolver configuration on its switches and routers. It exposes configuration data such as configured DNS server addresses, domain name, and domain search list used by the device's own name resolution. This is primarily a configuration-visibility MIB rather than a hardware/fault MIB, but it is still useful operationally: an unreachable or misconfigured DNS server object can explain why the device fails to resolve hostnames for logging, NTP, or management functions, effectively signaling a software/service-level fault. It has no dependency on other standard MIBs beyond the conventional SNMPv2-SMI table structure. It is deployed on Allied Telesis switches and routers in enterprise/campus networks where the device itself needs DNS resolution for management and logging services. Engineers can download the AT-DNS-CLIENT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in AT-DNS-CLIENT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Allied Telesis switch/router (management-plane DNS client)

Monitoring Examples

An administrator would poll the DNS server address objects and domain search list to confirm the switch is configured to query the correct resolvers, and check resolution status if reachability to management systems referenced by hostname starts failing. Finding a stale or unreachable DNS server address explains why syslog or NTP hostnames configured on the device fail to resolve.

What Can Be Monitored

configured DNS server addresses
default domain name
domain search list
DNS client resolver configuration

Imported Objects

From AT-SMI-MIB

modules

OBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddressType

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
atDns	1.3.6.1.4.1.207.8.4.4.4.501			Description.
atDNSClient	1.3.6.1.4.1.207.8.4.4.4.501.1			This MIB file contains definitions of managed objects for the Allied Telesis DNS Client configuration.
INT atDNSServerIndexNext	1.3.6.1.4.1.207.8.4.4.4.501.1.1	INTEGER	read-only	This object represents the next available value for the object 'atDNSServerIndex'. For creating an entry in the 'atDNSServerTable', a management application should read this object, get the value and use the same.
atDNSServerTable	1.3.6.1.4.1.207.8.4.4.4.501.1.2		not-accessible	This table contains information about the Domain Name System (DNS) Server configurations in the system.
atDNSServerEntry	1.3.6.1.4.1.207.8.4.4.4.501.1.2.1		not-accessible	An Entry representing the information about a DNS Server configuration.
INT atDNSServerIndex	1.3.6.1.4.1.207.8.4.4.4.501.1.2.1.1	INTEGER	not-accessible	This object represents the index corresponding to the particular DNS Server configuration in the system. For creation of new entry, the value of this object should be same as that of the value of 'atDNSServerIndexNext' object. If this is not the case, then the entry creation will fail.
IPt atDNSServerAddrType	1.3.6.1.4.1.207.8.4.4.4.501.1.2.1.2	InetAddressType	read-only	This object represents the Inet Address type of the 'atDNSServerAddr' object. It's value should be of the values list below: unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16)
IP atDNSServerAddr	1.3.6.1.4.1.207.8.4.4.4.501.1.2.1.3	IpAddress	read-write	This object represents the address of the DNS Server. This object is a current object for row creation. When a new row is created, this object is set with a default value '0.0.0.0', and the management application should change it to a desired value by a SET operation.
ROW atDNSServerStatus	1.3.6.1.4.1.207.8.4.4.4.501.1.2.1.4	RowStatus	read-write	The Status of this row. The reading of this object should have a value of 'active(1)', for an existing row. For creation of new entry, a management application should set this object with value 'createAndGo(4)', and using the same value as that got from reading object 'atDNSServerIndexNext', as the index for the new entry. When an entry is created, the object 'atDNSServerAddr' in the entry is set with a default value '0.0.0.0'. The management application should change it to a desired value with a SET operation. For deletion of entry, a management application should set this object with value 'destroy(6)'. Once an entry is deleted, other entries in the table which have bigger index than the deleted one, will be indexed again. Therefore a management application can effectively delete multiple entries by repeating the SET operation using the same index. An attempt to SET this object with value other than 'createAndGo' or 'destroy' will fail.

RFC description

Manages DNS client configuration including DNS server settings for Allied Telesis switches.

Start monitoring Allied Telesis switches/routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download AT-DNS-CLIENT-MIB

What Is AT-DNS-CLIENT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description