Digital Freight Portal
HomeAbout
  • What's new
  • 📚Resources
    • Guides
      • Getting Started
      • Margins
    • FAQ
    • Release Notes
      • Production branch
      • Next branch
    • Suggestions
    • Legal
      • Terms of Service
      • Privacy Policy
      • Cookie Policy
      • Sub-Processors
  • 👨‍💻 Developer Resources
    • Index
    • Guides
      • Quotation Widget
      • External authentication
      • Bring your own domain
    • API Documentation
Powered by GitBook
On this page
  • Introduction
  • Goal
  • What you'll need
  • Workflow
  • Choosing a domain name
  • Add a CNAME record to your DNS settings
  • Request domain configuration from DFP

Was this helpful?

  1. 👨‍💻 Developer Resources
  2. Guides

Bring your own domain

Personalize your portal by bringing your own domain.

PreviousExternal authentication

Last updated 1 year ago

Was this helpful?

Introduction

Available in advanced plans on stable branch only.

Contact your Sales Representative for more information

By default Digital Freight Portal will serve your portals instance as a self-chosen subdomain under qwykportals.com (or next.qwykportals.com) You can however elect to bind your own (sub-)domain and allow your visitor to access your portal using a URL they recognise as trusted.

CNAME records must always point to another domain name, never directly to an IP address.

Goal

The goal of this guide is to setup domain alias to point to your QwykPortals instance so people can use that address to visit your portal.

What you'll need

Workflow

Choosing a domain name

We recommend choosing a domain name that's not too long and easy to remember for your customers. This can be for example: portal.your-domain.com, or any variant of portal such as online or customers or we personally think my is really good.

For the purposes of this guide we'll choose my.digitalfreight.company as the domain at which we'd like the portal to be available.

CNAME records pointing to the apex of a zone are not permitted:

If you decide to register a fresh domain, you need to remember that creating a CNAME record at the apex of your zone (i.e. example.com) is not permitted and your DNS provider will likely not accept you creating one. If they do let you continue, the alias is unlikely to work.

Add a CNAME record to your DNS settings

Follow the provided steps provided by your DNS provider, creating a CNAME record for the domain you chose in the first step pointing to: hosting.qwykportals.com

NAME                              TYPE   VALUE
-----------------------------------------------------------------
my.digitalfreight.company.        CNAME  hosting.qwykportals.com.

Guides for common DNS providers:

If your DNS provider is not listed, you can either check their support page or use a search engine to search for "How to create a CNAME record on [YOUR DOMAIN PROVIDER]"

Do not create A records

Traffic to portals is load balanced to a fleet of servers at multiple IPs and due to auto-scaling those IP addresses change frequently. We will not notify you of changes and so when pointing an A to portals, the domain may become unable to resolve. Always use CNAMEs as explained above.

Request domain configuration from DFP

This is a paid feature. If it is included in your subscription, your Implementation Manager will assist with the setup during onboarding. If you'd like to add this feature to your subscription, please reach out to your Sales Representative who will assist you with the setup.

We use CNAME records to accomplish this which will also allow us to generate an SSL certificate using method:

A Canonical Name record (abbreviated as CNAME record) is a type of in the (DNS) that maps one domain name (an ) to another (the name).

This can prove convenient when running multiple services (like an and a , each running on different ports) from a single IP address. One can, for example, point ftp.example.com and www.example.com to the DNS entry for example.com, which in turn has an which points to the IP address. Then, if the IP address ever changes, one only has to record the change in one place within the network: in the DNS A record for example.com.

Source:

Let's Encrypt's HTTP-01 ACME Challenge
resource record
Domain Name System
alias
canonical
[1]
FTP server
web server
A record
https://en.wikipedia.org/wiki/CNAME_record
A domain to forward to your portal.
Access to your hosting or name provider's DNS settings to create a CNAME record.
A domain redirection request sent to onboarding@qwyk.io
AWS Route53
BlueHost
Domain.com
DreamHost
GoDaddy
Google Domains
HostGator
Namecheap
One.com
A standard portals url with your own chosen prefix but our root.
A custom domain