The nuu:bit platform can be used for servicing individual web domains of a web property (for example, “www.company.com”, “static1.company.com”, “static2.company.com”, etc) or, maintaining the whole web property using a single primary domain (like “www.company.com”) by utilizing nuu:bit's 3rd-party links aggregation feature.
The on-boarding of a web domain on the nuu:bit platform is typically composed of the following steps, performed either by customer using nuu:bit’s self-provisioning customer portal https://portal.nuubit.net/
- Provisioning of default nuu:bit configuration for a new domain. The step requires the following information to be specified or provided by the customer:
- The web domain to be served by nuu:bit (for example, “www.company.com”)
- The IP address or domain name of customer origin web server to be used to fetch the web content from (for example, “www-origin.company.com” or “220.127.116.11”)
- The HTTP “Host:” header value to be used to fetch the website content from the origin web server (if the value should be different from the configured domain name)
- The geographic location of the customer’s origin web server (to be used to select the closest Rev’s first-mile location)
- Each newly provisioned customer domain is automatically assigned with a corresponding CNAME in domain “NUUBITCN.NET”. The CNAME name is composed of the provisioned domain name and domain “NUUBITCN.NET”. For example, if the customer domain name is “static.company.com” the generated CNAME name will be “STATIC.COMPANY.COM.NUUBITCN.NET”. Later the CNAME record should be used by the customer to send the domain’s traffic to Rev’s content acceleration platform.
- 1st optional step - adjusting of Rev edge caching rules. In the default configuration, nuu:bit will respect HTTP caching configuration specified in web origin server responses (set in HTTP response headers). If the origin web server does not set proper caching headers it is possible to adjust nuu:bit edge and browser caching behavior using pretty sophisticated caching configuration mechanism provided by Rev.
- 2nd optional step - configuration of aggregation of third-party web links. If the website uses third-party objects hosted on separate domains (like static objects, JS libraries or independent third-party services like Google Analytics or Optimizely) it is possible to aggregate the domains under the website’s primary domain name.
- 3rd optional step - provisioning of SSL configuration for the domain. If the customer website is utilizing SSL encryption to protect the website content it is required to provision the nuu:bit service with an SSL certificate matching the website’s domain name, either FQDN (like “www.company.com”) or wildcard (like “*.company.com”). Currently, the operation should be performed by Rev’s Customer Support team, and it takes about 20 minutes to complete.
- Testing the prepared nuu:bit configuration by pointing the web domain locally to a nuu:bit edge proxy server. The step allows customers to confirm that nuu:bit service is properly configured to serve his website, and to verify website performance, caching rules, content optimization settings, etc.
- Once happy with the testing results - change DNS record for the domain to point to nuu:bit’s CNAME.
Boarding via self-provisioning customer portal
Once you’ve registered the account, proceed with the configuration setup over the https://portal.nuubit.net/ web page. Please refer to the provisioning of default nuu:bit configuration of a new domain.
To view the current domains list, please click the Web link on the left-hand side menu of the nuu:bit portal.
Adding a new domain
To add a new domain, please click the Add New Domain button and specify the required fields as shown in the figure below.
You need to fill out the following fields when adding a new domain:
- The particular Web domain served by nuu:bit (www.illustration.com).
- The IP address or origin server DNS name which is used to fetch the web content from it.
- Origin host header is used to get the website content from the original website server.
- The geographic location of the customer’s origin web server which is used to select the nearest first-mile site.
Once you filled in all the necessary details, please confirm the domain addition by clicking the Create Domain button.
Editing a domain
To edit the existing domain, please click the Edit domain button as shown in the figure below.
Then, modify the appropriate fields and specify the necessary details. All fields are self-documenting by moving the cursor over the field in question.
When you click on Update (not "Publish") button in the domain and SSL certificate configuration forms the updated configuration it sent to the staging environment. Publish will publish the configuration to production.
You can also configure the particular domain by clicking the Advanced Edit domain button.
The advanced view format allows you to view the parameters set in JSON format, as displayed on the figure below.
You can edit all the necessary details in a more specific way. Once all the changes are done, please click the Update button.
Modifying DNS record for your website
To use nuu:bit with your website, change the DNS record for the domain to point it to the nuu:bit CNAME. For example, the CNAME record for 'www.illustration.com' domain corresponds to 'www.illustration.com.revdn.net'. This will enable directing your website traffic to the nuu:bit platform.
Traffic analytics reports
As a result, you’ll be able to track the appropriate values over the Proxy Traffic reports as shown in the figure below.
Please choose the corresponding report category in the left-side panel menu.
Once you’ve completed all the steps, you should be able to manage your newly created domain. Please refer to the Documentation section for further configuration. If you experience any issue, please contact our Customer Support team.