Subdomain Requests

Creation and maintenance guidelines

Subdomains can be created for the following entities:

  • Colleges
  • Departments (Academic or non-academic)
  • TAMU System entities
  • "Permanent" University research organizations
  • [e.g.,]

Once a subdomain is created, all names associated with the organization's machines should be moved underneath the subdomain as soon as possible. This will allow the Departmental IT staff to manage their hosts in Infoblox directly. The organization is responsible for updating the configurations of affected machines to reflect the shift into the subdomain.

Authority of any new subdomains will not be delegated. In other words, the DNS zone must be managed by the Division of IT through Infoblox. This restriction is necessary to avoid technical problems that arise in the management of the inverse namespace.

Subdomains that are not used will be candidates for deletion. If after a one year period none of the hosts within a subdomain are active, the subdomain will be marked to indicate non-use. The organization associated with the subdomain will be contacted before the subdomain is removed.

3rd Level Sub-Domains

3rd Level Sub-Domains, or sub-domains below the departmental level, are available in Infoblox. These subdomains typically fall directly under the departmental subdomain and are owned by the same group. Permissions for these would be inherited. In Infoblox, this domain level is seen as part of the hostname. For example, the name will show up in the zone / srg as figment.private.

A zone or shared record group will be made for permissions only.

Departmental Approvals

Colleges, Agencies and Departments will be asked to provide the names of the individuals allowed to approve requests for sub-domains and creation of hosts in the name space. These names will be referenced on the Division of IT’s ServiceNow Service Catalogs Request Forms. To update the departmental approvals, send an email to