When you first create a Synap Portal, you will be asked to choose a unique subdomain on the Synap website, such as:

myportal.synap.ac

(In the above example, myportal is the subdomain).

However, if your plan allows, you can also configure Synap so that it can be accessed from a subdomain of your own website, such as:

practice.mywebsite.com 


This feature is available with all Standard and Enterprise accounts. To take advantage of it, you will need to add two DNS records to your domain name. If you are not sure what this is, then speak to your website manager / developer, or your Synap account manager who will be able to help.

Steps

1) Choosing a Subdomain

First, you need to check whether a Custom Domain is included in your plan, and then you will need to decide what you want your subdomain to be. This can be anything you want, as long as it is not already in use by another part of your website. We recommend choosing something fairly short and easy to remember.

Some examples are listed below:

  • practice (practice.mywebsite.com)
  • learn (learn.mywebsite.com)
  • synap (synap.mywebsite.com)
  • courses (courses.mywebsite.com)

Once you have decided on a subdomain, let your Synap account manager know, so that we can generate an authentication record to add.

2) Installing the DNS Records

Once you have let us know your desired subdomain, we will give you two DNS records to add to your website hosting.

The first of these is a CNAME record that points from your subdomain to the Synap server. You should add it with the following settings:

Type: CNAME

Name: practice (or whatever subdomain you have chosen)

Value: app.synap.ac.

TTL: 300 (or as low as you can set it)

Note: the name of the record ('practice' in the example above) will change depneding on which subdomain you have chosen. Furtheremore, depending on your DNS registrar, you may need to enter the whole domain in this field, i.e. practice.mywebsite.com, however most DNS registrarss automatically add this in, so you should only need to add the subdomain itself.

The screenshot below shows an example of this record being installed using the Amazon Route53 DNS registrar, but if you are using another system such as GoDaddy or 123Reg, the steps will be almost identical.

Once you have done this, there is a second DNS record to add - the steps are exactly the same, but the record contains a randomly generated string which sometimes causes confusion. This second record is important as it authorises us to add your subdomain to our SSL ceetificate, which means that your site will be secure (i.e. sent via HTTPS).

The Name and Value fields of these records are unique to each client, but we have provided an example one below (note DO NOT install this on your DNS registrar, it is here as an example only)

Type: CNAME

Name: _467f77d8ebb437c7ce70910d85bf54a3.practice.mywebsite.com.

Value: _3104b746df3ff14b2dc2ee6af180ed5b.tfmgdnztqk.acm-validations.aws.

TTL: 300 (or as low as you can set it)

Note how there is a randomly generated string at the beginning of both the name and the value, which stats with an underscore.

For the Value, the whole string should be entered, starting with the underscore (_) and ending with .acm-validations.aws.

For the Name, you probably do not need to enter '.mywebsite.com' - as above, your DNS provider will probably pre-fill this for you, but check your settings and speak to your developer if you are not sure.

3) Watch & Wait

Whilst you will often see a result within an hour, it can take upto 48 hours for new DNS changes to fully propagate. In the meantime, you can still access your Synap site from the old subdomain, and we will let you know when the new domain is ready :)

Did this answer your question?