idnits 2.17.1 draft-ietf-dns-mibext-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 58 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 292 has weird spacing: '... field octet...' == Line 316 has weird spacing: '...l. For examp...' == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (November 12, 1992) is 11487 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 12 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft - DNS MIB - November 12, 1992 4 DNS MIB Extensions 6 12-November-1992 8 DNS Working Group 10 Rob Austein 11 Epilogue Technology Corporation 12 sra@epilogue.com 14 Jon Saperia 15 Digital Equipment Corporation 16 saperia@tcpjon.ogo.dec.com 18 Status of this Memo 20 This document is an Internet Draft. Internet Drafts are working 21 documents of the Internet Engineering Task Force (IETF), its 22 Areas, and its Working Groups. Note that other groups may also 23 distribute working documents as Internet Drafts. Internet Drafts 24 are draft documents valid for a maximum of six months. Internet 25 Drafts may be updated, replaced, or obsoleted by other documents 26 at any time. It is not appropriate to use Internet Drafts as 27 reference material or to cite them other than as a "working 28 draft" or "work in progress." Please check the I-D abstract 29 listing contained in each Internet Draft directory to learn the 30 current status of this or any other Internet Draft. 32 This draft document will be submitted to the RFC editor as 33 a proposed extension to the SNMP MIB. Distribution of this 34 document is unlimited. Please send comments or corrections to 35 the authors. 37 Abstract 38 This memo defines a set of DNS (Domain Name System) exten- 39 sions that have been created for the Internet MIB. When used 40 in conjunction with the Structure of Management Information (RFC 41 1155), the Management Information Base for Network Management 42 of TCP/IP-based internets (RFC 1213) and the Simple Network 43 Management Protocol (RFC 1157), it will be possible to provide 44 integrated network management of DNS resolver and server soft- 45 ware in standard TCP/IP based environments. This document was 46 produced by the DNS working group. 48 Digital Equipment Corporation 49 Maynard, Massachusetts 51 ii Document Expiration Date - May 17, 1993 - Austein, Saperia 52 CONTENTS 54 1 Introduction......................................... 1 56 2 The DNS Model........................................ 1 58 3 Selected Objects..................................... 3 60 4 Objects.............................................. 4 62 4.1 Format of Definitions............................. 5 64 4.2 Textual Conventions............................... 5 66 5 Object Definitions................................... 6 68 6 Acknowledgements..................................... 66 70 7 References........................................... 66 72 iii 73 1 Introduction 75 With the adoption of The Simple Network Management Protocol (RFC 76 1157), the Management Information Base for network management of 77 TCP/IP-based internets (RFC 1213), and the Structure of Manage- 78 ment Information (RFC 1155) by the Internet, and a large number 79 of vendor implementations of these standards in commercially 80 available products, it became possible to provide a higher level 81 of effective network management in TCP/IP-based internets than 82 previously available. With the growth in the use of these stan- 83 dards, it has become possible to consider the management of 84 other elements of the infrastructure beyond the basic TCP/IP 85 protocols. A key element of the TCP/IP infrastructure is the 86 DNS. 88 Up to this point there has been no mechanism to integrate the 89 management of the DNS with SNMP-based managers. This memo pro- 90 vides the mechanisms by which IP-based management stations can 91 effectively manage DNS client and server software in an inte- 92 grated fashion through the use of the standard Internet SMI, MIB 93 and Simple Network Management Protocol. 95 New DNS MIB objects have been defined to be used in conjunction 96 with the Internet MIB to allow access and control of the DNS via 97 SNMP by the Internet community. 99 2 The DNS Model 101 In theory, the DNS world is pretty simple. There are two kinds 102 of entities: resolvers and name servers. Resolvers ask ques- 103 tions. Name servers answer them. The real world, however, is not 104 so simple. Implementors have made widely differing choices about 105 how to divide DNS functions between resolvers and servers. They 106 have also constructed various sorts of exotic hybrids. The most 107 difficult task in defining this MIB was to accommodate this wide 108 range of entities without having to come up with a separate MIB 109 for each. 111 Document Expiration Date - May 17, 1993 - Austein, Saperia 1 112 We divided up the various DNS functions into two, non- 113 overlapping classes, called 'resolver functions' and 'name 114 server functions'. A DNS entity that performs what we define 115 as resolver functions contains a resolver, and therefore must 116 implement the MIB groups required of all resolvers. Some re- 117 solvers also implement 'optional' functions such as a cache. In 118 this example, they will also implement the cache group contained 119 in this MIB. A DNS entity which implements name server functions 120 is considered to be a name server, and must implement the MIB 121 groups required for name servers. If the same piece of software 122 performs both resolver and server functions, we imagine that it 123 contains both a resolver and a server. 125 In our model, a resolver is a program (or piece thereof) which 126 obtains resource records from servers. Normally it does so at 127 the behest of an application, but may also do so as part of its 128 own operation. A resolver sends DNS protocol queries and re- 129 ceives DNS protocol replies. A resolver neither receives queries 130 nor sends replies. A full service resolver is one that knows 131 how to resolve queries: it obtains the needed resource records 132 by contacting a server authoritative for the records desired. 133 A stub resolver does not know how to resolve queries: it sends 134 all queries to a local name server, setting the recursion de- 135 sired flag to indicate that it hopes that the name server will 136 be willing resolve the query. A resolver may (optionally) have 137 a cache for remembering previously acquired resource records. 138 It may also have a negative cache for remembering names or data 139 that have been determined not to exist. 141 A name server is a program (or piece thereof) that provides 142 resource records to resolvers. All references in this document 143 to 'a name server' imply 'the name server's role'. (In some 144 cases the name server's role and the resolver's role might 145 be combined into a single program.) A name server receives 146 DNS protocol queries and sends DNS protocol replies. A name 147 server neither sends queries nor receives replies. As a con- 148 sequence, name servers do not have caches. Normally, a name 149 server would expect to receive only those queries for which it 151 2 Document Expiration Date - May 17, 1993 - Austein, Saperia 152 could respond to with authoritative information. However, if 153 a name server receives a query that it cannot respond to with 154 purely authoritative information, it may choose to try to obtain 155 the necessary additional information from a resolver which may 156 or may not be a separate process. 158 3 Selected Objects 160 Many of the objects included in this memo have been created from 161 information contained in the DNS specification. The DNS spec- 162 ification is found in Domain Names - Concepts and Facilities 163 (RFC 1034) and Domain Names - Implementation and Specification 164 (RFC 1035), as amended and clarified by Requirements for In- 165 ternet Hosts - Application and Support (RFC1123). Additional 166 usage information is found in the Domain Administrators Guide 167 (RFC 1032), and the Domain Administrators Operations Guide (RFC 168 1033). Other objects have been created based on experience with 169 existing DNS management tools, expected operational need, and 170 the statistics generated by existing DNS implementations. These 171 objects have been ordered into groups as follows: 173 o General Configuration Group 175 o Resolver Configuration Group 177 o Server Configuration Group 179 o Resolver Counter Group 181 o Server Counter Group 183 o Records Group 185 o Resolver Cache Group 187 o Resolver Negative Cache Group 189 o Resolver Statistics Group 191 Document Expiration Date - May 17, 1993 - Austein, Saperia 3 192 o Server Management Group 194 The ordering of objects into these groups reflects the DNS model 195 in which the resolver and server functions can be separate 196 pieces of code which may or may not reside on the same host. 197 This approach accommodates common implementations such as BIND, 198 but it is not constrained by that or any other implementation 199 paradigm. 201 Some of the objects defined in this memo have been created from 202 information contained in existing configuration files used by 203 many DNS implementations. This information has been converted 204 into a standard form using the Internet Standard SMI defined in 205 RFC 1155. 207 4 Objects 209 The objects in this memo are described using the standard Inter- 210 net SMI and BER of RFC 1155. Each object description includes 211 the objects name, its syntax and encoding. Just as with objects 212 supported in the MIB (RFC 1156), an object name is identified 213 with an object identifier which has been administratively as- 214 signed. This identifies an Object Type. When an object type 215 is combined with a specific instance - the particular object 216 is uniquely identified. Use of Object Descriptors in this memo 217 is consistent with that of RFC 1156 - meaning that they are 218 text strings meant to be read by humans. The descriptors have 219 been created from a variety of sources. For the most part, the 220 descriptions are influenced by by the DNS related RFCs noted 221 above. For example, the descriptors for counters used for the 222 various types of queries of DNS records are influenced by the 223 definitions used for the various record types found in Domain 224 Names - Implementation and Specification RFC 1035. 226 4 Document Expiration Date - May 17, 1993 - Austein, Saperia 227 4.1 Format of Definitions 229 An object in this memo is specified by five fields of informa- 230 tion: Object, Syntax, Description, Access, and Status. 232 The OBJECT is a textual name (OBJECT DESCRIPTOR) for that ob- 233 ject type combined with an administratively obtained OBJECT 234 IDENTIFIER. 236 SYNTAX : For each object type, its abstract syntax is presented 237 using the ASN.1 specified in RFC 1155. 239 DESCRIPTION: A general description of the object type. 241 ACCESS : The standard access keywords supported in RFC 1156 are 242 used. The keywords used in this MIB are: read-only, read-write, 243 and not-accessible. 245 STATUS : The status field is used to describe with a single 246 keyword whether the object type is mandatory or optional. Status 247 keywords of obsolete and deprecated are not used in this memo 248 since this is the first version of the DNS MIB. 250 4.2 Textual Conventions 252 Several datatypes have been introduced as a textual conven- 253 tions in this DNS MIB document. These additions will facilitate 254 the common understanding of information used by the DNS. No 255 changes to the SMI or the SNMP are necessary to support these 256 conventions which are described in 5.0 (Object Definitions). 258 Document Expiration Date - May 17, 1993 - Austein, Saperia 5 259 5 Object Definitions 261 RFCxxxx-dnsMIB 263 DEFINITIONS ::= BEGIN 265 IMPORTS 266 mgmt, NetworkAddress, IpAddress, 267 Counter, Gauge, TimeTicks 268 FROM RFC1155-SMI 269 DisplayString, mib-2 270 FROM RFC1213-MIB 271 OBJECT-TYPE 272 FROM RFC-1212; 274 -- DNS MIB 276 dns OBJECT IDENTIFIER ::= { experimental 9999 } 278 -- textual conventions 280 DnsDate ::= OCTET STRING (SIZE (8 | 11)) 281 -- This data type is intended to provide a consistent 282 -- method of reporting date information. The information 283 -- is organized as follows: the first two octets represent 284 -- the year, the next two are for the month and day of the 285 -- year. The next three octets are for hours, minutes and 286 -- seconds. The next octet is for deci-seconds. Direction 287 -- from UT is in the next octet. The next two octets are for 288 -- hours and minutes from UT. Note that in systems which do not 289 -- track UT, they will return only the first 8 octets. The table 290 -- below is intended to help to make clear this convention. 291 -- 292 -- field octets contents range 293 -- 1 1-2 year 0..65536 294 -- 2 3 month 1..12 295 -- 3 4 day 1..31 296 -- 4 5 hour 0..23 297 -- 5 6 minutes 0..59 298 -- 6 7 seconds 0..60 300 6 Document Expiration Date - May 17, 1993 - Austein, Saperia 301 -- (use 60 for leap-second) 302 -- 7 8 deci-seconds 0..9 303 -- 8 9 direction from UT "+" / "-" 304 -- 9 10 hours from UT 0..11 305 -- 10 11 minutes from UT 0..59 306 -- For example, Tuesday May 26, 1992 at 1:30:15 PM EDT could 307 -- be displayed as on a management station: 308 -- 1992-5-26,13:30:15.0,-4:0 310 DnsName ::= OCTET STRING 311 -- A DNS name is a sequence of labels. When DNS names are displayed, 312 -- the boundaries between labels are typically indicated by dots (e.g. 313 -- "Acme" and "COM" are labels in the name "Acme.COM" ). In the DNS 314 -- protocol, however, no such separators are needed because each label 315 -- is encoded as a length octet followed by the indicated number of 316 -- octets of label. For example, "Acme.COM" is encoded as the octet 317 -- sequence { 4, 'A', 'c', 'm', 'e', 3, 'C', 'O', 'M', 0 } (the final 318 -- 0 is the length of the name of the root domain, which appears 319 -- implicitly at the end of any DNS name). This MIB uses the same 320 -- encoding as the DNS protocol. 322 -- A DnsName must always be a fully qualified name. It is an error to 323 -- encode a relative domain name as a DnsName without first making it a 324 -- fully qualified name. 326 DnsClass ::= INTEGER (0..65535) 327 -- This data type is used to represent the class values which appear 328 -- in Resource Records in the DNS. A 16-bit unsigned integer is 329 -- used to allow room for new classes of records to be defined. 330 -- Existing standard classes are listed in the DNS specification. 332 DnsType ::= INTEGER (0..65535) 333 -- This data type is used to represent the type values which appear 334 -- in Resource Records in the DNS. A 16-bit unsigned integer is 335 -- used to allow room for new record types to be defined. 336 -- Existing standard types are listed in the DNS specification. 338 Document Expiration Date - May 17, 1993 - Austein, Saperia 7 339 DnsQClass ::= INTEGER (0..65535) 340 -- This data type is used to represent the QClass values which appear 341 -- in Resource Records in the DNS. A 16-bit unsigned integer is 342 -- used to allow room for new QClass records to be defined. Existing 343 -- standard Qclasses are listed in the DNS specification. 345 DnsQType ::= INTEGER (0..65535) 346 -- This data type is used to represent the QType values which appear 347 -- in Resource Records in the DNS. A 16-bit unsigned integer is 348 -- used to allow room for new QType records to be defined. 349 -- Existing standard QTypes are listed in DNS specification. 351 DnsTime ::= INTEGER 352 -- DnsTime values are 32-bit unsigned integers which measure time in 353 -- seconds. 355 DnsValid ::= INTEGER { valid (1), clear (2) } 356 -- Many of the tables in this MIB have as one of their columns, an 357 -- object which can be set to a value of 2 to delete that 358 -- row of the table. If a read operation is performed on this 359 -- object, a value of 1 is returned to indicate a valid row in the 360 -- table. 362 DnsOpCode ::= INTEGER (0..15) 363 -- This data type is used to represent the DNS OPCODE used in the 364 -- header section of DNS messages. Existing standard OPCODE values 365 -- are listed in the DNS specification. 367 DnsRespCode ::= INTEGER (0..15) 368 -- This data type is used to represent the DNS RCODE value in response 369 -- messages. Existing standard RCODE values are listed in the DNS 370 -- specification. 372 -- groups in the dns mib 374 8 Document Expiration Date - May 17, 1993 - Austein, Saperia 375 dnsGenConfig OBJECT IDENTIFIER ::= { dns 1 } 376 dnsResConfig OBJECT IDENTIFIER ::= { dns 2 } 377 dnsServConfig OBJECT IDENTIFIER ::= { dns 3 } 378 dnsResCounter OBJECT IDENTIFIER ::= { dns 4 } 379 dnsServCounter OBJECT IDENTIFIER ::= { dns 5 } 380 dnsRec OBJECT IDENTIFIER ::= { dns 6 } 381 dnsResCache OBJECT IDENTIFIER ::= { dns 7 } 382 dnsResNCache OBJECT IDENTIFIER ::= { dns 8 } 383 dnsResStats OBJECT IDENTIFIER ::= { dns 9 } 384 dnsServMgmt OBJECT IDENTIFIER ::= { dns 10 } 386 -- General Configuration Group 388 -- The implementation of the General Configuration group is 389 -- mandatory for all systems. 391 dnsGenConfigDnsUse OBJECT-TYPE 392 SYNTAX INTEGER { 393 primary (1), 394 not-primary (2), 395 not-used (3) 396 } 397 ACCESS read-write 398 STATUS mandatory 399 DESCRIPTION 400 "A value of 1 indicates that the DNS is used as the 401 primary mechanism for name resolution on this system. 402 A 2 indicates that some other mechanism is used as the 403 primary mechanism for name resolution and that the DNS 404 is used as a back-up. A value of 3 indicates that DNS 405 is not used for name resolution." 406 ::= { dnsGenConfig 1 } 408 Document Expiration Date - May 17, 1993 - Austein, Saperia 9 409 -- Resolver Configuration Group 411 -- The implementation of the Resolver Configuration group is 412 -- mandatory for all systems which implement any resolver software 413 -- functions. 415 dnsResConfigImplementIdent OBJECT-TYPE 416 SYNTAX DisplayString 417 ACCESS read-only 418 STATUS mandatory 419 DESCRIPTION 420 "The implementation identification string for the resolver 421 software in use on the system, for example; RES2.1" 422 ::= { dnsResConfig 1 } 424 dnsResConfigService OBJECT-TYPE 425 SYNTAX INTEGER { 426 recursive-only (1), 427 iterative-only (2), 428 recursive-and-iterative (3) 429 } 430 ACCESS read-only 431 STATUS mandatory 432 DESCRIPTION 433 "Kind of DNS resolution service provided. 434 RECURSIVE-ONLY indicates a stub resolver. 435 ITERATIVE-ONLY indicates a normal full service resolver. 436 RECURSIVE-AND-ITERATIVE indicates a full service resolver 437 which performs a mix of recursive and iterative queries." 438 ::= { dnsResConfig 2 } 440 dnsResConfigMaxCnames OBJECT-TYPE 441 SYNTAX INTEGER 442 ACCESS read-write 443 STATUS mandatory 444 DESCRIPTION 445 "Limit on how many CNAMEs the resolver should allow before 446 deciding that there's a CNAME loop. Zero means that 447 resolver has no explicit CNAME limit." 448 ::= { dnsResConfig 3 } 450 10 Document Expiration Date - May 17, 1993 - Austein, Saperia 451 -- DNS Resolver Seat Belt Table 453 dnsResConfigSeatBeltTable OBJECT-TYPE 454 SYNTAX SEQUENCE OF DnsResConfigSeatBeltEntry 455 ACCESS not-accessible 456 STATUS mandatory 457 DESCRIPTION 458 "Table of safety belt information used by the resolver 459 when it hasn't got any better idea of where to send a 460 query, such as when the resolver is booting or is a stub 461 resolver." 462 ::= { dnsResConfig 4 } 464 dnsResConfigSeatBeltEntry OBJECT-TYPE 465 SYNTAX DnsResConfigSeatBeltEntry 466 ACCESS not-accessible 467 STATUS mandatory 468 DESCRIPTION 469 "An entry in the resolver's seatbelt table." 470 INDEX { dnsResConfigSeatBeltAddr, 471 dnsResConfigSeatBeltSubTree, 472 dnsResConfigSeatBeltClass } 473 ::= { dnsResConfigSeatBeltTable 1 } 475 DnsResConfigSeatBeltEntry ::= 476 SEQUENCE { 477 dnsResConfigSeatBeltAddr 478 IpAddress, 479 dnsResConfigSeatBeltName 480 DnsName, 481 dnsResConfigSeatBeltSvc 482 INTEGER, 483 dnsResConfigSeatBeltPref 484 INTEGER, 485 dnsResConfigSeatBeltSubTree 486 DnsName, 487 dnsResConfigSeatBeltClass 488 DnsClass, 489 dnsResConfigSeatBeltFile 491 Document Expiration Date - May 17, 1993 - Austein, Saperia 11 492 OCTET STRING, 493 dnsResConfigSeatBeltDate 494 DnsDate, 495 dnsResConfigSeatBeltValid 496 DnsValid 497 } 498 dnsResConfigSeatBeltAddr OBJECT-TYPE 499 SYNTAX IpAddress 500 ACCESS read-only 501 STATUS mandatory 502 DESCRIPTION 503 "The IP address of the SeatBelt name server identified 504 by this row of the table." 505 ::= { dnsResConfigSeatBeltEntry 1 } 507 dnsResConfigSeatBeltName OBJECT-TYPE 508 SYNTAX DnsName -- OCTET STRING 509 ACCESS read-only 510 STATUS mandatory 511 DESCRIPTION 512 "The DNS name of a SeatBelt nameserver identified by this 513 row of the table. A value of NULL indicates that the name 514 is not known by the resolver." 515 ::= { dnsResConfigSeatBeltEntry 2 } 517 dnsResConfigSeatBeltSvc OBJECT-TYPE 518 SYNTAX INTEGER { 519 iterative (1), 520 recursive (2), 521 recursive-and-iterative (3) 522 } 523 ACCESS read-only 524 STATUS mandatory 525 DESCRIPTION 526 "Type-Of-Service resolver expects from seatbelt 527 nameserver. 528 ITERATIVE indicates that resolver will be directing 529 iterative queries to this name server (RD bit turned 530 off). 532 12 Document Expiration Date - May 17, 1993 - Austein, Saperia 533 RECURSIVE indicates that resolver will be directing 534 recursive queries to this name server (RD bit turned 535 on). 536 RECURSIVE-AND-ITERATIVE indicates that the resolver will 537 be directing both recursive and iterative queries to the 538 server identified in this row of the table." 539 ::= { dnsResConfigSeatBeltEntry 3 } 541 dnsResConfigSeatBeltPref OBJECT-TYPE 542 SYNTAX INTEGER 543 ACCESS read-only 544 STATUS mandatory 545 DESCRIPTION 546 "This value identifies the preference for the server 547 identified in this row of the table. The lower the 548 value, the more desirable the particular server is 549 considered." 550 ::= { dnsResConfigSeatBeltEntry 4 } 552 dnsResConfigSeatBeltSubTree OBJECT-TYPE 553 SYNTAX DnsName -- OCTET STRING 554 ACCESS read-only 555 STATUS mandatory 556 DESCRIPTION 557 "Queries sent to the Seatbelt name server identified by 558 this row of the table are limited to those for names 559 in the name subtree identified by this variable. If no 560 such limitation applies, the value of this variable is 561 the name of the root domain." 562 ::= { dnsResConfigSeatBeltEntry 5 } 564 dnsResConfigSeatBeltClass OBJECT-TYPE 565 SYNTAX DnsClass -- INTEGER (0..65535) 566 ACCESS read-only 567 STATUS mandatory 568 DESCRIPTION 569 "The class of DNS queries that will be sent to the 570 server identified by this row of the table." 571 ::= { dnsResConfigSeatBeltEntry 6 } 573 Document Expiration Date - May 17, 1993 - Austein, Saperia 13 574 dnsResConfigSeatBeltFile OBJECT-TYPE 575 SYNTAX OCTET STRING 576 ACCESS read-only 577 STATUS mandatory 578 DESCRIPTION 579 "The name of the file from which the information in 580 this row of the table was last initialized or updated. 581 The value is NULL if information came from a source other 582 than a configuration file." 583 ::= { dnsResConfigSeatBeltEntry 7 } 585 dnsResConfigSeatBeltDate OBJECT-TYPE 586 SYNTAX DnsDate -- DisplayString 587 ACCESS read-only 588 STATUS mandatory 589 DESCRIPTION 590 "The date and time that the file named by the 591 dnsResConfigSeatBeltFile variable for this row had last 592 been updated at the time that this row was last initialized 593 or updated. The value is NULL if unknown or not applicable 594 because the dnsResConfigSeatBeltFile variable is NULL." 595 ::= { dnsResConfigSeatBeltEntry 8 } 597 dnsResConfigSeatBeltValid OBJECT-TYPE 598 SYNTAX DnsValid 599 ACCESS read-write 600 STATUS mandatory 601 DESCRIPTION 602 "Setting this variable to CLEAR deletes this SeatBelt 603 server." 604 ::= { dnsResConfigSeatBeltEntry 9 } 606 -- Server Configuration Group 608 -- The implementation of the Server Configuration Group is 609 -- mandatory for all systems which implement DNS server software 610 -- functions. 612 14 Document Expiration Date - May 17, 1993 - Austein, Saperia 613 dnsServConfigImplementIdent OBJECT-TYPE 614 SYNTAX DisplayString 615 ACCESS read-only 616 STATUS mandatory 617 DESCRIPTION 618 "The implementation identification string for the DNS 619 server software in use on the system, for example; 620 FNS2.1" 621 ::= { dnsServConfig 1 } 623 dnsServConfigRecurs OBJECT-TYPE 624 SYNTAX INTEGER { 625 available (1), 626 restricted (2), 627 unavailable (3) 628 } 629 ACCESS read-write 630 STATUS mandatory 631 DESCRIPTION 632 "This represents the recursion status of requests made 633 to this server. The possible values are: available - 634 performs recursion on requests from clients. 635 Restricted - recursion is performed on requests only 636 from certain clients, for example; clients on an access 637 control list. Unavailable - recursion is not available." 638 ::= { dnsServConfig 2 } 640 -- Resolver Counters Group 642 -- The implementation of the Resolver Counters Group is mandatory for 643 -- all systems which implement resolver functions 645 Document Expiration Date - May 17, 1993 - Austein, Saperia 15 646 dnsResCounterUpTime OBJECT-TYPE 647 SYNTAX DnsTime 648 ACCESS read-only 649 STATUS mandatory 650 DESCRIPTION 651 "If the resolver has a persistent state, e.g., a 652 process; this value will be the time elapsed since it 653 started. For software that does not have persistence, 654 this value will be 0." 655 ::= { dnsResCounter 1 } 657 dnsResCounterResetTime OBJECT-TYPE 658 SYNTAX DnsTime 659 ACCESS read-only 660 STATUS mandatory 661 DESCRIPTION 662 "Elapsed time since cache was reloaded." 663 ::= { dnsResCounter 2 } 665 dnsResCounterInUpkts OBJECT-TYPE 666 SYNTAX Counter 667 ACCESS read-only 668 STATUS mandatory 669 DESCRIPTION 670 "Number of UDP packets received by the resolver 671 process(s)." 672 ::= { dnsResCounter 3 } 674 dnsResCounterOutUPkts OBJECT-TYPE 675 SYNTAX Counter 676 ACCESS read-only 677 STATUS mandatory 678 DESCRIPTION 679 "Number of UDP packets sent by the resolver 680 process(s)." 681 ::= { dnsResCounter 4 } 683 16 Document Expiration Date - May 17, 1993 - Austein, Saperia 684 dnsResCounterTCPInitiatns OBJECT-TYPE 685 SYNTAX Counter 686 ACCESS read-only 687 STATUS mandatory 688 DESCRIPTION 689 "Number of attempts to initiate TCP connections with 690 servers." 691 ::= { dnsResCounter 5 } 693 dnsResCounterInTCPMesgs OBJECT-TYPE 694 SYNTAX Counter 695 ACCESS read-only 696 STATUS mandatory 697 DESCRIPTION 698 "Number of received DNS messages over TCP by the 699 resolver process." 700 ::= { dnsResCounter 6 } 702 dnsResCounterOutTCPMesgs OBJECT-TYPE 703 SYNTAX Counter 704 ACCESS read-only 705 STATUS mandatory 706 DESCRIPTION 707 "Number of out bound DNS messages sent over TCP by the 708 resolver." 709 ::= { dnsResCounter 7 } 711 -- Resolver Counter Table 713 dnsResCounterTable OBJECT-TYPE 714 SYNTAX SEQUENCE OF DnsResCounterTableEntry 715 ACCESS not-accessible 716 STATUS mandatory 717 DESCRIPTION 718 "Table of the current count of resolver queries and 719 answers." 720 ::= { dnsResCounter 8 } 722 Document Expiration Date - May 17, 1993 - Austein, Saperia 17 723 dnsResCounterTableEntry OBJECT-TYPE 724 SYNTAX DnsResCounterTableEntry 725 ACCESS not-accessible 726 STATUS mandatory 727 DESCRIPTION 728 "Entry in the resolver counter table. Entries are 729 indexed by dns OpCode." 730 INDEX { dnsResCounterOpCode } 731 ::= { dnsResCounterTable 1 } 733 DnsResCounterTableEntry ::= 734 SEQUENCE { 735 dnsResCounterOpCode 736 DnsOpCode, 737 dnsResCounterQueries 738 Counter, 739 dnsResCounterResponses 740 Counter 741 } 742 dnsResCounterOpCode OBJECT-TYPE 743 SYNTAX DnsOpCode -- INTEGER (0..15) 744 ACCESS read-only 745 STATUS mandatory 746 DESCRIPTION 747 "The index to this table. The OpCodes that have 748 already been defined are found in RFC1035." 749 ::= { dnsResCounterTableEntry 1 } 751 dnsResCounterQueries OBJECT-TYPE 752 SYNTAX Counter 753 ACCESS read-only 754 STATUS mandatory 755 DESCRIPTION 756 "Number of queries [total] that have sent out by the 757 resolver since initialization for the OpCode which is 758 the index to this row of the table." 759 ::= { dnsResCounterTableEntry 2 } 761 18 Document Expiration Date - May 17, 1993 - Austein, Saperia 762 dnsResCounterResponses OBJECT-TYPE 763 SYNTAX Counter 764 ACCESS read-only 765 STATUS mandatory 766 DESCRIPTION 767 "Number of responses [total] that have been received 768 by the resolver since initialization for the OpCode 769 which is the index to this row of the table." 770 ::= { dnsResCounterTableEntry 3 } 772 -- Resolver Response Code Counter Table 774 dnsResResponseTable OBJECT-TYPE 775 SYNTAX SEQUENCE OF DnsResResponseTableEntry 776 ACCESS not-accessible 777 STATUS mandatory 778 DESCRIPTION 779 "Table of the current count of responses to resolver 780 queries." 781 ::= { dnsResCounter 9 } 783 dnsResResponseTableEntry OBJECT-TYPE 784 SYNTAX DnsResResponseTableEntry 785 ACCESS not-accessible 786 STATUS mandatory 787 DESCRIPTION 788 "Entry in the resolver response table. Entries are 789 indexed by DNS response code." 790 INDEX { dnsResResponseCode } 791 ::= { dnsResResponseTable 1 }