⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc1611.txt

📁 bind 9.3结合mysql数据库
💻 TXT
📖 第 1 页 / 共 4 页
字号:
   DnsOpCode ::= TEXTUAL-CONVENTION       STATUS  current       DESCRIPTION               "This textual convention is used to represent the DNS               OPCODE values used in the header section of DNS               messages.  Existing standard OPCODE values are listed in               the DNS specifications."       REFERENCE               "RFC-1035 section 4.1.1."       SYNTAX  INTEGER (0..15)   DnsRespCode ::= TEXTUAL-CONVENTION       STATUS  current       DESCRIPTION               "This data type is used to represent the DNS RCODE value               in DNS response messages.  Existing standard RCODE               values are listed in the DNS specifications."       REFERENCE               "RFC-1035 section 4.1.1."       SYNTAX  INTEGER (0..15)Austein & Saperia                                               [Page 8]RFC 1611               DNS Server MIB Extensions                May 1994   -- Server Configuration Group   dnsServConfigImplementIdent OBJECT-TYPE       SYNTAX      DisplayString       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "The implementation identification string for the DNS               server software in use on the system, for example;               `FNS-2.1'"       ::= { dnsServConfig 1 }   dnsServConfigRecurs  OBJECT-TYPE       SYNTAX      INTEGER { available(1),                             restricted(2),                             unavailable(3) }       MAX-ACCESS  read-write       STATUS      current       DESCRIPTION               "This represents the recursion services offered by this               name server.  The values that can be read or written               are:               available(1) - performs recursion on requests from               clients.               restricted(2) - recursion is performed on requests only               from certain clients, for example; clients on an access               control list.               unavailable(3) - recursion is not available."        ::= { dnsServConfig 2 }   dnsServConfigUpTime OBJECT-TYPE       SYNTAX      DnsTime       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "If the server 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 zero."       ::= { dnsServConfig 3 }   dnsServConfigResetTime OBJECT-TYPE       SYNTAX      DnsTime       MAX-ACCESS  read-only       STATUS      currentAustein & Saperia                                               [Page 9]RFC 1611               DNS Server MIB Extensions                May 1994       DESCRIPTION               "If the server 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 name server was               `reset.'  For software that does not have persistence or               does not support a `reset' operation, this value will be               zero."       ::= { dnsServConfig 4 }   dnsServConfigReset OBJECT-TYPE       SYNTAX      INTEGER { other(1),                             reset(2),                             initializing(3),                             running(4) }       MAX-ACCESS  read-write       STATUS      current       DESCRIPTION               "Status/action object to reinitialize any persistant name               server state.  When set to reset(2), any persistant               name server state (such as a process) is reinitialized as               if the name server 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) - server in some unknown state;                   initializing(3) - server (re)initializing;                   running(4) - server currently running."       ::= { dnsServConfig 5 }   -- Server Counter Group   dnsServCounterAuthAns OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of queries which were authoritatively answered."       ::= { dnsServCounter 2 }   dnsServCounterAuthNoNames OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of queries for which `authoritative no such name'               responses were made."       ::= { dnsServCounter 3 }Austein & Saperia                                              [Page 10]RFC 1611               DNS Server MIB Extensions                May 1994   dnsServCounterAuthNoDataResps OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of queries for which `authoritative no such data'               (empty answer) responses were made."       ::= { dnsServCounter 4 }   dnsServCounterNonAuthDatas OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of queries which were non-authoritatively               answered (cached data)."       ::= { dnsServCounter 5 }   dnsServCounterNonAuthNoDatas OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of queries which were non-authoritatively               answered with no data (empty answer)."       ::= { dnsServCounter 6 }   dnsServCounterReferrals OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of requests that were referred to other servers."       ::= { dnsServCounter 7 }   dnsServCounterErrors OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of requests the server has processed that were               answered with errors (RCODE values other than 0 and 3)."       REFERENCE               "RFC-1035 section 4.1.1."       ::= { dnsServCounter 8 }   dnsServCounterRelNames OBJECT-TYPE       SYNTAX      Counter32Austein & Saperia                                              [Page 11]RFC 1611               DNS Server MIB Extensions                May 1994       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of requests received by the server for names that               are only 1 label long (text form - no internal dots)."       ::= { dnsServCounter 9 }   dnsServCounterReqRefusals OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of DNS requests refused by the server."       ::= { dnsServCounter 10 }   dnsServCounterReqUnparses OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of requests received which were unparseable."       ::= { dnsServCounter 11 }   dnsServCounterOtherErrors OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of requests which were aborted for other (local)               server errors."       ::= { dnsServCounter 12 }   -- DNS Server Counter Table   dnsServCounterTable OBJECT-TYPE       SYNTAX      SEQUENCE OF DnsServCounterEntry       MAX-ACCESS  not-accessible       STATUS      current       DESCRIPTION               "Counter information broken down by DNS class and type."       ::= { dnsServCounter 13 }   dnsServCounterEntry OBJECT-TYPE       SYNTAX      DnsServCounterEntry       MAX-ACCESS  not-accessible       STATUS      current       DESCRIPTION               "This table contains count information for each DNS classAustein & Saperia                                              [Page 12]RFC 1611               DNS Server MIB Extensions                May 1994               and type value known to the server.  The index allows               management software to to create indices to the table to               get the specific information desired, e.g., number of               queries over UDP for records with type value `A' which               came to this server.  In order to prevent an               uncontrolled expansion of rows in the table; if               dnsServCounterRequests is 0 and dnsServCounterResponses               is 0, then the row does not exist and `no such' is               returned when the agent is queried for such instances."       INDEX     { dnsServCounterOpCode,                   dnsServCounterQClass,                   dnsServCounterQType,                   dnsServCounterTransport }       ::= { dnsServCounterTable 1 }   DnsServCounterEntry ::=       SEQUENCE {           dnsServCounterOpCode               DnsOpCode,           dnsServCounterQClass               DnsClass,           dnsServCounterQType               DnsType,           dnsServCounterTransport               INTEGER,           dnsServCounterRequests               Counter32,           dnsServCounterResponses               Counter32           }   dnsServCounterOpCode OBJECT-TYPE       SYNTAX      DnsOpCode       MAX-ACCESS  not-accessible       STATUS      current       DESCRIPTION               "The DNS OPCODE being counted in this row of the table."       ::= { dnsServCounterEntry 1 }   dnsServCounterQClass OBJECT-TYPE       SYNTAX      DnsClass       MAX-ACCESS  not-accessible       STATUS      current       DESCRIPTION               "The class of record being counted in this row of the               table."       ::= { dnsServCounterEntry 2 }Austein & Saperia                                              [Page 13]RFC 1611               DNS Server MIB Extensions                May 1994   dnsServCounterQType OBJECT-TYPE       SYNTAX      DnsType       MAX-ACCESS  not-accessible       STATUS      current       DESCRIPTION               "The type of record which is being counted in this row in               the table."       ::= { dnsServCounterEntry 3 }   dnsServCounterTransport OBJECT-TYPE       SYNTAX      INTEGER { udp(1), tcp(2), other(3) }       MAX-ACCESS  not-accessible       STATUS      current       DESCRIPTION               "A value of udp(1) indicates that the queries reported on               this row were sent using UDP.               A value of tcp(2) indicates that the queries reported on               this row were sent using TCP.               A value of other(3) indicates that the queries reported               on this row were sent using a transport that was neither               TCP nor UDP."       ::= { dnsServCounterEntry 4 }   dnsServCounterRequests OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of requests (queries) that have been recorded in               this row of the table."       ::= { dnsServCounterEntry 5 }   dnsServCounterResponses OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of responses made by the server since               initialization for the kind of query identified on this               row of the table."       ::= { dnsServCounterEntry 6 }Austein & Saperia                                              [Page 14]RFC 1611               DNS Server MIB Extensions                May 1994   -- Server Optional Counter Group   -- The Server Optional Counter Group is intended for those systems   -- which make distinctions between the different sources of the DNS   -- queries as defined below.   --   -- Objects in this group are implemented on servers which distinguish   -- between queries which originate from the same host as the server,   -- queries from one of an arbitrary group of hosts that are on an   -- access list defined by the server, and queries from hosts that do   -- not fit either of these descriptions.   --   -- The objects found in the Server Counter group are totals.  Thus if   -- one wanted to identify, for example, the number of queries from   -- `remote' hosts which have been given authoritative answers, one   -- would subtract the current values of ServOptCounterFriendsAuthAns   -- and ServOptCounterSelfAuthAns from servCounterAuthAns.   --   -- The purpose of these distinctions is to allow for implementations   -- to group queries and responses on this basis.  One way in which   -- servers may make these distinctions is by looking at the source IP   -- address of the DNS query.  If the source of the query is `your   -- own' then the query should be counted as `yourself' (local host).   -- If the source of the query matches an `access list,' the query   -- came from a friend.  What constitutes an `access list' is   -- implementation dependent and could be as simple as a rule that all   -- hosts on the same IP network as the DNS server are classed   -- `friends.'   --   -- In order to avoid double counting, the following rules apply:   --   -- 1. No host is in more than one of the three groups defined above.   --   -- 2. All queries from the local host are always counted in the   --    `yourself' group regardless of what the access list, if any,   --    says.   --   -- 3. The access list should not define `your friends' in such a way   --    that it includes all hosts.   That is, not everybody is your   --    `friend.'   dnsServOptCounterSelfAuthAns OBJECT-TYPE       SYNTAX      Counter32       MAX-ACCESS  read-only       STATUS      current       DESCRIPTION               "Number of requests the server has processed which               originated from a resolver on the same host for whichAustein & Saperia                                              [Page 15]

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -