Associate a custom domain

All Fresco sites are built with a default URL that ends in '.site.ox.ac.uk'.  When requesting your Fresco website you must select a simple prefix (comprising of only letters and numbers) to create a URL like 'shortcode.site.ox.ac.uk'.  

Should you find that this default platform address is not suitable for your website launch, you have the option to agree a custom domain address with your approvers/comms team, and request that it be associated with your Fresco site. You cannot request this until after your site has been created.  

To agree, validate, associate and secure a custom domain address for a Fresco site is a five step process.  As domain registration and hosting is separate to web-hosting and is largely managed independently of the Fresco CMS Platform, the initial steps need to be done before contacting the Fresco service team.  

Summary of the process

  1. Ensure that the address you wish to use (e.g. project.department.ox.ac.uk) complies with University Policy and local web governance arrangements .
  2. Check with your local IT team whether they already own the parent domain/subdomain (e.g. department.ox.ac.uk) or if they will take on ownership.  If it needs registering as a new domain/subdomain or transferring in to the University DNS then they should work with the Domains team as per OxIntranet guidance on Domains Registration. 
  3. Use the Fresco Self Service form to request that Fresco service team activate platform security for your chosen custom domain. They will need to work with your local IT team to validate it. 
  4. When you are ready to launch your site, ask your local IT team to configure the custom domain to point at Fresco. 
  5. Improve your SEO by setting the custom domain as your website's Primary Domain

These steps must be done in order, and completed in sufficient time before you plan to launch the custom domain. Step 3 is carried out fortnightly by the Fresco Service team, so you must have completed validation at least 2 weeks before you need the custom domain working.  If you are migrating to Fresco from an existing website then step 4 should be scheduled for when you want your site to go live.  

Please note: A maximum of two custom domains are allowed for a Fresco site. Making the total three (inclusive of the platform .site.ox.ac.uk domain)

More details

When a new website is created in Fresco, it is provisioned with a platform address of:

<prefix>.site.ox.ac.uk

where <prefix> has the value that was supplied on the Site Request form - Request a site | Fresco CMS.

This address is suitable to be used as a public web address for your site. Using the <prefix>.site.ox.ac.uk domain means the site is automatically covered by the Fresco Platform's main SSL Security Certificate. In this case, there is no need to register another address and you are good-to-go in putting your site live whenever you are ready to do so.

However, in some cases it is desirable to have a web address that is more tailored, e.g.

  • As a part of an existing Oxford University domain, i.e. <prefix>.<existingdomain>.ox.ac.uk
  • To create a new Oxford University domain, i.e. www.<newdomain>.ox.ac.uk
  • An external domain outside of *.ox.ac.uk, e.g. www.<newdomain>.org.uk

If you are replacing a website that already has its own domain name, this address can be set up with Fresco platform security in preparation and then be configured to point to your Fresco site when you are ready to go-live.

When choosing a custom domain for any website that will be published on University web systems then it must comply with University DNS Naming Policy.  This includes local University policy (web pages should be within the web structure of the department responsible whenever possible) and also policies laid down by the appropriate domain registries and domain registrars (i.e. for .com, .org, .net, .uk) and JANET policy (for .ac.uk).

Please follow all advice here: DNS naming policy

Approval for new domains: Please note that new domain names must be approved by the appropriate Head of Department or Head of House. Some requests may have to be referred to other bodies within the University.

Pre-requisite: The domain or subdomain must be registered in the University's DNS - this means externally-registered domains need to be transferred in to the University's DNS

To register a new domain or transfer-in an existing externally registered domain, contact domains@it.ox.ac.uk. Ensure that your request has been appropriately approved before making the request and explain that the site you will use the domain on will be a Fresco site.

If you are transferring-in a domain name from an external registrar, you should supply details of that registrar so that the Domains team can organise the transfer.

To register a new part to an existing domain, contact the local web manager of the existing domain in the first instance. Management of unit sub-domains is often devolved to local IT managers who will be able to deal with your request, liaising with the central Domains team as needed on your behalf. 

See the DNS domain registration page for more information.

Fresco supports HTTPS-only meaning when any custom domain is added to a Fresco site, it must also be added to the Fresco platform SSL Security Certificate. If this is not done, when viewed using the custom domain, the website will display security alerts in web browsers.

To add a custom domain to Fresco's SSL Certificate - whether as part of a site's go-live or at any other time - use the <Link to custom domain SR> form to ask for a domain to be added to the Fresco SSL Certificate.

The Fresco platform SSL Certificate is updated every week. When the request is received, the domain will be added to a list of domains waiting to be added to the Certificate, and added in the subsequent update.

If you want to add your custom domain to the SSL Certificate but you are not sure whether you will be ready to use the domain by the following certificate update period, let us know anyway. We can add it to the certificate in advance, and it won't take effect until the domain is pointed to your site.

Notice

To be added to the SSL Security Certificate, the domain must be registered by the University Domain Registrar.

Please note: six-part custom domains are not supported. 

(e.g <prefix>.<department>.<sub-department>.ox.ac.uk)

For the purposes of the SSL certificate, bare and fully-qualified versions of a domain are considered as two separate domains. Either are acceptable for use with your website. Please specify the domain you intend to use on the website.

Examples of bare domains vs fully-qualified domains:

  • (bare) example.ox.ac.uk | (fully-qualified) researchlab.example.ox.ac.uk
  • (bare) project.ac.uk | (fully-qualified) www.project.ac.uk

The custom domain needs a DNS record to be created or edited to point to the Fresco content delivery network, so that when a web user follows a link or bookmark containing the domain, they are taken to the Fresco platform.  You should only do this after the security configuration for the domain has been completed by the Fresco Service team.

Once this DNS pointing record is configured, hits on your custom address will be routed to your Fresco site. You should therefore only request this when you are ready to launch the site – you should allow time to complete your go-live steps. 

Responsibility for DNS record management is devolved to University units, so requests to point domains at the Fresco platform need to be sent to your local IT Support Staff (ITSS). 

Your local IT team should know if they are treating your new/transferred address as a "fully-qualified domain" or a "bare domain" (one that is also used for non-website purposes).  This will dictate which type of record they will create.  When you are ready, ask your IT team to create a DNS record with a target/content of site.ox.ac.uk. It can be of either type CNAME or ANAME, but they must use ANAME if they plan to use the address as a bare domain. 

Refer to Primary domains (Fresco Help)

Was this page helpful?  University members can provide feedback on our documentation by submitting a feedback form