School's own and manage their own domains, thus the DNS updates are generally the responsibility of the school. However, most DNS hosts do allow you to invite a delegate, contributor, or technical contact to have management access. If you need Rediker to assist with the DNS for your website go live, please check with your DNS host to see if you are able to add a delegate or technical contact. Below are the basic DNS records necessary for pointing a domain to our RediSite platform. As DNS providers and interfaces vary, you will need to check with your provider about specific directions, support, and or details about managing DNS records (Some links provided at the bottom of this article as a convenience).
Before proceeding with your website go live please read the following:
- Please do not proceed with the DNS updates to go live with your RediSite unless you have informed Rediker of a planned go live date and time. Simply send an email to [email protected] or [email protected].
- After updating your DNS there are final go live steps to be done by Rediker, it is imperative that you notify Rediker 24-hrs (when possible) ahead of your DNS updates.
- DNS should only be edited and updated by someone with technical knowledge, mistakes or editing the wrong records can result in the breaking of other domain services like email.
- Rediker is not a domain registrar nor has access to a school's domain, unless you grant us access as an agent or contact on your account.
- Rediker is not responsible for managing your school's DNS records, and can only assist and advise on records necessary for our own products and services.
- Updating DNS records can and often will result in down-time for your website. This is out of our control, and is a natural part of DNS updates. The time and length of any down-time varies by DNS host. Please plan such updates accordingly.
- Most DNS hosts allow you to lower your TTL settings to help expedite changes, however, that does not always guarantee a faster go live process. Check with your DNS host about updating TTL settings.
Take a screenshot, write down, or copy your current DNS records before changing, deleting, or adding any records. This can help put things back to the way they were IF any mistakes are made.
We use and require 3 records in your DNS in order for your domain to point and resolve to your RediSite hosted with Rediker. Use the following information for the CNAME record and A records:
CNAME
- Host: www
- Points to: s.multiscreensite.com
Note: You cannot have two WWW records as they will conflict. If you have a WWW record from a previous website or as a default, it will need to be removed in order to add our record.
A Records
- First A Record:
- Host/Alias: @
- Target/Destination: 35.172.94.1
- Second A Record:
- Host/Alias: @
- Target/Destination: 100.24.208.97
Note: If you have an IP from a previous website, host, or default, you may need to remove that record or it will conflict with routing your domain to the new RedSite.
Two A Records are used for server balance and redundancy.
Here is an example of how your DNS screen may look after adding the required records. Note that this varies by host and other records you may have.
Final steps like issuing an SSL certificate for the website, can only happen once the correct DNS records are entered and have propagated on the web. While this process can take less than a few hours, however, it may take up to 48hrs.
Below are some common domain hosts (registrars) and links to their instructions for configuring DNS settings.
| Domain Host | Support Links |
GoDaddy | CNAME A Records |
Network Solutions | CNAME and A Records |
| Cloudflare | CNAME and A Records Note: Make sure the proxy option is turned off to avoid potential connection and SSL issues. Here is a note about the CloudFlare encryption setting. |
Squarespace Domains | CNAME A Records |
NameCheap | CNAME A Records |