There are actually 4 ways to "capture" a tklapp.com hostname (i.e. sub.tklapp.com), and the one you choose depends on your use case:
Launching via Hub: When you launch a server via the Hub you set the hostname you want to associate with the server. The Hub handles the rest.
Launching via the Hub CLI: If you use hubtools, when executing hub-launch you can specify the fqdn to be associated with your server (--fqdn=sub.tklapp.com).
Post Launch via Hub: If you have servers already launched via the Hub before we released the domain functionality (or if you "release" an association), in the server record under Hostname, click None - it will display a dialog where you can associate a hostname.
Non-Hub deployment: The HubDNS client can be installed on any TKL deployment, say in a VM or on bare-metal. When initializing you specify a FQDN, it will contact the Hub and do it's thing. You can then configure hourly automatic updates, essentially making it a Dynamic DNS client.
If you want to use your own domain (ie. something besides tklapp.com), you will need to add it to your Hub cloud account. The Hub will walk you through the steps, it's pretty simple.
There are actually 4 ways to "capture" a tklapp.com hostname...
There are actually 4 ways to "capture" a tklapp.com hostname (i.e. sub.tklapp.com), and the one you choose depends on your use case:
If you want to use your own domain (ie. something besides tklapp.com), you will need to add it to your Hub cloud account. The Hub will walk you through the steps, it's pretty simple.