Locality Domain Names in TX.US Administered by the Texas Regional Hostmaster $Id: locality.tx.us.names,v 1.4 2000/05/04 06:38:20 hostmast Exp hostmast $ SCOPE This document outlines the requirements for applications in any locality domain names administrated by Texas Regional Hostmaster. There are two types of locality domain names that are administrated by Texas Regional Hostmaster on behalf of the US-Domain: governmental entities (city or county governments) and all others. REQUIREMENTS The general requirements for any name in the US-Domain are outlined in the following RFCs: RFC 1480 - THE US DOMAIN URL: ftp://ftp.ns.gen.tx.us/pub/rfc/rfc1480.txt RFC 1591 - THE DOMAIN NAME SYSTEM STRUCTURE AND DELEGATION URL: ftp://ftp.ns.gen.tx.us/pub/rfc/rfc1591.txt RFC 2146 - U.S. GOVERNMENT INTERNET DOMAIN NAMES URL: ftp://ftp.ns.gen.tx.us/pub/rfc/rfc2146.txt Multiple word names are connected by a dash (e.g. Joe's Garage in El Paso would become joes-grarage.el-paso.tx.us and Custom Frames in DeSoto would become custom-frames.de-soto.tx.us). All domain names must be unique and must comply with relevant RFCs regarding domain names. All applications in the locality domains must show a relevant administrative contact employed by the organization making use of the name. For a city government, this must be the mayor, city manager or city information technology director. For a county government, this must be the county judge or county information technology director. For all other entities, it should be the chief executive officer, the chief operating officer or the head of the company's information technology department. Delegations of zones within an undelegated city or county government zone require specific authorization of the city mayor or county judge respectively. Finally, the requesting organization must have a mailing address located within the locality. The administrative contact and technical contact are not required to have a postal address in the locality. As part of processing the application for an govenmental entity (county or city government), it may be necessary to request confirmation from the chief administrative official (mayor or county judge). This is typically done via fax. Without confirmation, the application will not be processed and will be presumed to be unauthorized by the governmental entity. Any name server listed in the application must be operational and ready to service for the domain listed in the application prior to sending the application. The email address listed in the SOA must be valid. If there is an MX or A record directly associated with the domain name itself, then "postmaster@domain-name" must resolve to a valid mailbox. No delegation will happen until all the technical problems with the domain as outlined in this paragraph (and the relevant RFCs) are resolved. Currently, there are no registration or maintenance charges for domain names in the locality name space. However, this situation could change. Please check with via email to "hostmaster@ns.gen.tx.us" if you have any questions on this change or any other policy changes concerning locality delegation. Note that there are some locality delegations that took place prior to this requirements document that have names that violate the requirements detailed here. Those delegations are grandfathered and those organizations may continue to operate using the grandfathered names. However, organizations with such delegations are encouraged to apply for names that are in compliance with this policy to insure uniform and correct operation of the DNS and other facilites that depend on such names being in a documented format going forward. Applications can be obtained at this URL: http://www.ns.gen.tx.us/cgi-bin/template.pl ============================================================================ TABLE: .TX.US DOMAIN NAMING STRUCTURE ============================================================================ ..TX.US = locality based names .CI..TX.US = locality; city gov. agencies .CO..TX.US = locality; county gov. agencies