8.5

Edit

DNS name configuration

Example of domain names which need to be assigned to the servers (DNS names are for example purpose only. There are no specific requirements for DNS names).

Domain Name (Example)Record TypeDescription
db.example.comA or CNAMEDB Server
*.db.example.comadditional A or CNAME record for DB server*required to access S3 emulator URLs like this some-bucket.db.example.com
app.example.comA or CNAMEAPP Server
apm.example.comA or CNAMEAPM Server
ocr.example.comA or CNAMEOCR Server
vds-standalone.example.comA or CNAMEVDS standalone server (master + slave)
vds-master.example.comA or CNAMEFor installing VDS in cluster mode. There might be multiple VDS Slave servers. DNS records should be created for all of them.
vds-slave.example.comA or CNAME
rpa.example.comA or CNAMERPA server
bi.example.comA or CNAMEBI server (Analytics)

In case when several roles are going to be installed on one server, the server must have all domain names that match the roles which will be installed.

Alternative way 1

If wildcard Domain name (*.db.example.com) is not possible to assign with your DNS provider, please add the following DNS records (IP addresses are for example purpose only):

Domain NameCNAME or IP
db.example.com192.168.1.1
app.example.com192.168.1.2
apm.example.com192.168.1.3
ocr.example.com192.168.1.4
vds-standalone.example.com192.168.1.5
rpa.example.com192.168.1.6
bi.example.com192.168.1.7
crowdcontrol.taglib.db.example.comdb.example.com
cv-help.db.example.comdb.example.com
doc-upload.db.example.comdb.example.com
logos.crowdcomputing.db.example.comdb.example.com
public.crowdcontrol.db.example.comdb.example.com
secdocs.db.example.comdb.example.com
tinymce-resources.db.example.comdb.example.com
vds-models.db.example.comdb.example.com
vds-resources.db.example.comdb.example.com
workfusion-resources.db.example.comdb.example.com
workfusiondevelopment.db.example.comdb.example.com
workspace-resources.db.example.comdb.example.com

Alternative way 2

If you can't use DNS service for any resson, add the records into hosts files on each server and end users' PCs which will use the product:

  • On Linux machines: edit the /etc/hosts file.
  • On Windows machines: edit C:/Windows/system32/drivers/etc/hosts file.

IP Addresses below are for example purpose. You should use your real IP addresses. Add the following records to the hosts files:

Example:

192.168.1.1        db.example.com
192.168.1.2        app.example.com
192.168.1.3        apm.example.com
192.168.1.4        ocr.example.com
192.168.1.5        vds.example.com
192.168.1.6        rpa.example.com
192.168.1.7        bi.example.com

192.168.1.1       crowdcontrol.taglib.db.example.com
192.168.1.1       cv-help.db.example.com
192.168.1.1       doc-upload.db.example.com
192.168.1.1       logos.crowdcomputing.db.example.com
192.168.1.1       public.crowdcontrol.db.example.com
192.168.1.1       secdocs.db.example.com
192.168.1.1       tinymce-resources.db.example.com
192.168.1.1       vds-models.db.example.com
192.168.1.1       vds-resources.db.example.com
192.168.1.1       workfusion-resources.db.example.com
192.168.1.1       workfusiondevelopment.db.example.com
192.168.1.1       workspace-resources.db.example.com
← PreviousNext →