Domain Name Service - Best Practices Department of Network and Communication Services University of Utah October 23, 2000 I. Domain Name Service Domain Name Service, or DNS, is the system by which a computer or host's name is mapped to its IP address, for name-to-address translation. The University of Utah's DNS server maintains a database of domain names (host names) and their corresponding IP addresses. II. Operational Authority and Responsibility at the University of Utah The overall operational responsibility and administration of domain name service (DNS) for University of Utah domain entities shall lie with the Department of Network and Communications Services (NetCom). The following is a current list of University-held domains: Utah.edu UofU.net 110.128.in-addr.arpa 97.155.in-addr.arpa 98.155.in-addr.arpa 99.155.in-addr.arpa 100.155.in-addr.arpa 101.155.in-addr.arpa III. Obtaining a Third Level Name Under the utah.edu Domain A. General criteria for third level names Since 1991, the name service group has made a practice of evaluating requests for new third level names (either individual machines or sub-domains) on a case-by-case basis. There have always been some informal considerations when evaluating such requests. The following are some stated criteria that generally must be met before granting the new name request. 1. The requesting organizational entity is a functional, operational unit of the University of Utah, officially recognized by the University, such as a college or academic or administrative department. There should be direct accountability of the entity to University administration. 2. The requested name is a sub-domain representing the requesting organization, or representing a service name that is of interest to a significant population either within or outside of the University. (Groups on campus serving groups off campus not on behalf of the University might consider obtaining an .ORG domain.) 3. There is no existing sub-domain of utah.edu to which the requesting organization might belong. 4. Both administrative and technical personnel within the department are aware of the domain request and are agreed on the name. 5. If the requested name is reminiscent of a different department or function on campus, that entity has released all claim on the sub-domain. 6. The requested name is consistent with the "reasonable names" criteria talked about below. 7. The requesting entity must agree to provide NetCom with up to date and current point-of-contact information for both technically and administratively responsible entity(s) overseeing the service name or sub-domain. B. Fourth-level domain names If the requesting entity cannot meet the criteria for an organization or functional group or a universal service, then NetCom asks the entity to seek a fourth level domain name under that of their department or college or other existing third level entity. IV. Reasonable Domain Names A. Generally In general, any name associated with the University of Utah needs to reflect positively on the University, and should not denigrate or reflect poorly the image of the University of Utah in any way. B. Specifically In the following, hostname also applies to any third level name or sub domain. 1. As recommended in RFC 1035, section 2.3.1, hostnames should start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphens. 2. Underscores and special characters should be avoided. 3. Eligible entities may request registration of hostnames of their choice, providing that the names: a. comply with all applicable University regulations; b. refer to their own department or organization, or to a project managed by the department or organization; c. do not imply affiliation with a campus unit or department with which the entity is not affiliated; and, d. are not currently in use. V. Delegation of in-addr Zones and Sub-domains to Departmental Name Servers A. Name service through NetCom NetCom encourages all departments or other entities that manage name space under the utah.edu domain or any of the associated in-addr zones to rely on NetCom for name service, and to make use of the NetCom-supplied tools for management of that namespace. B. Departmental name servers For zones that are currently delegated to departmental name servers, those name servers should be run in compliance with any recommendations of the Institutional Security Office regarding secure hosts and other specific recommendations regarding DNS servers. Maintainers of name servers should be acquainted with the relevant Internet documents, such as RFC 1034, RFC 1035 and RFC 1173. C. Point of Contact information NetCom requires those who maintain name servers to make their point-of-contact information available to NetCom, ISO and the Campus Helpdesk, and to keep the information current. Point of Contact registration and database services can be accessed through the NetCom website. D. Temporary withdrawal of DNS delegation Netcom may temporarily rescind a DNS delegation if the malfunction of a delegated name server is causing operational problems for all or part of the campus network and the responsible administrators cannot be immediately notified. In this event, NetCom will make every effort to notify the departmental administrators, using available contact information, of the change in delegation. E. Permanent revocation of DNS delegation NetCom may permanently rescind a delegation if there are repeated or consistent operational problems with delegated name servers. In these cases, departmental administrators will be given notice by the Director of NetCom, providing the reason(s) for the revocation. VI. Use of Campus Name Servers to Host Other Domains If an organization is a campus organization or entity, as outlined above and more specifically defined here: An organization or entity that is a functional, operational unit of the University of Utah, officially recognized by the University, such as a college, academic or administrative department, with direct accountability of the entity to University administration, is then eligible for domain name service through the University of Utah. Then, if that entity holds domains in support of non-profit educational endeavors, it should be deemed appropriate that campus-run and -operated name servers could be registered with the Internic and used to respond authoritatively to DNS requests for that domain. Currently, the Internic authorities have prescribed that such domains should exist under the .ORG or .NET top- level extensions. However, because of the volatile nature of top-level domains at this time, it is preferable not to make a blanket statement regarding top-level extensions, with the exception that it is highly unlikely that a domain ending with a .COM should be hosted by a campus name server.