Domain Name Server (DNS) CNAME Alias
The library can use a domain that they have registered rather than the assigned domain provided.
For example, Wheeljack Public Library’s hosted calendar might default to a provided URL of wheeljack.events.mylibrary.digital, but library wishes to have the public instead see a subdomain of their existing site http://www.wjlib.info, e.g. http://calendar.wjlib.info.
To facilitate this, the library needs to create 2 DNS records.
- A DNS CNAME record for the address they want the platform to appear under. In the previous example, if they have the domain wjlib.info and they want the platform to be located at calendar.wjlib.info, then they need to create a DNS CNAME record for “calendar” that points to the platform-provided events address (e.g. wheeljack.events.mylibrary.digital)
- A custom DNS record that allows for the generation of SSL certificates automatically with our platform hosting provider. The necessary information is different for each library/domain and will be provided during the implementation phase.
Using the example above, Wheeljack Public Library would be provided information like the following, where each x represents a unique set of alphanumeric or special characters generated by our platform (note that the actual Name and Value content will be different).
Record Type: CNAME Record Name: xxxxxxxxxxxxxxxxxxxxx.calendar.wjlib.info Record Value: xxxxxxxxxxxxxxxxxxxxx.acm-validations.aws
With those two records in place, the library will be able to use the URL from their own domain (e.g. calendar.wjlib.info) and load our hosted calendar platform seamlessly so that it appears to be a part of the library’s own website.