skip to content

The following is the per section, per field help available on the form, plus some additional details.

1) Details of requester

This section provides details of the person making the request and their institution so that they can be contacted, their Relationship Manager can be determined, and if appropriate an institutional sub-domain can be identified.

School/College: (drop-down list)
If more than one, please select lead institution.
Other - please specify: (if not on drop-down list)

Requesting institution(s):
Name of Department, College, Official University Institute, SRNs, SRIs etc. managing the request. This will normally be an existing institution, but if there is none, use

Current institution(s) sub-domains:
Normally consult your Computer Officer and/or other guidance to identify relevant existing subdomains (e.g. for the requesting or related institution). If requesting a domain name within (check the guidelines above to ensure that this is appropriate) or, if the previous answer is, enter 'Not applicable'.

Requester name: (autofilled)
First name and Surname

Requester CRSid: (autofilled)
e.g. as used for Raven

Requester email address: (autofilled)
If different from

2) Details of domain name requested

This section asks for details of the domain name being requested and what it is to be used for.

Domain name requested:
Consult your Computer Officer and/or other guidance for naming clashes, options, requirements for support for proposed names (e.g. - unique NEWNAME, SUBDOMAIN from institution, group etc.) Please see our guidelines for requesting domain names within

Requested for: (Website; Mail domain; Website and Mail domain; Other)
Consult your Computer Officer and/or other guidance for website, managed mail domain, other (e.g. other mail, collaboration systems). Please see our guidelines for requesting domain names within
If 'Other' Please Specify.

Level of domain: (Within institution; Within Special Domain, e.g.; Top level domain under; Other)
Please see guidelines for requesting domain names within
If 'Other' Please Specify.

Brief summary of planned use:
e.g. new institution, strategic research group, move/expansion/renaming

3) Person providing official support for this request

This section asks for details of the person with appropriate authority who is providing official support for the request. We may for example need to check details of their support with them.

Role of person supporting request:
The request must be supported by someone with appropriate authority for the level of domain, e.g.: Head of Institution or CO administering an institutional domain for a sub-domain of this; an academic or academically-related member of staff for etc; VC, a PVC, or the Registrary for a top-level @cam. Please see our guidelines for requesting domain names within

Name of person supporting request:

Email address of person supporting request:

Their email address in case we need to contact them. This can either be a personal email, e.g., or a role address, e.g.

4) Contacts

This section asks for information about who will run the domain (both contacts must be provided and will default to the requester) and how urgently it is needed (we will do our best, but the date given cannot be guaranteed).

Admin contact(s) and CRSid(s): (autofilled to include the requester)
Minimum of 1 reachable member of staff

Technical contact(s) and CRSid(s): (autofilled to include the requester)
Minimum of 1 reachable member of staff

Planned launch date:
To give an indication of the urgency. We cannot promise to meet very tight timescales.

UIS Service Desk

UIS Service Status

Phone padded  Service status line: (01223 7)67999
Website  Sign up for SMS/email status alerts
Website  Read major IT incident reports

UIS bITe-size bulletin

A regular newsletter aimed at the University's IT community, highlighting service and project news from UIS.

Sign up >

Latest news

University Wireless Service maintenance: Tuesday 21 September, 08:00–09:00

16 September 2021

The University Wireless Service will be undergoing essential maintenance between 08:00 and 09.00 on Tuesday 21 September while we apply a security software patch. This is a security update to ClearPass, which provides Wireless Service network access control. We're not expecting any disruption to service, but it should be...

Mailing list migrations from Mailman to Sympa

31 August 2021

We intend to migrate all remaining lists associated with colleges from Mailman to Sympa during the week commencing 13 September 2020. The current total is 1,567. How this will affect users of the mailing list management service Most mailing list subscribers shouldn't notice any difference. During the switchover, there will...

Managed Zone Service closedown and migration to Mythic Beasts

24 August 2021

The Managed Zone Service (MZS) is being shut down, and its data content migrated to a commercial provider, Mythic Beasts. There will be no interruption to the service, but MZS users in institutions will need to make arrangements to retain management access to their zones. What is changing? UIS set up the MZS many years ago...