9.0

Edit

DNS name configuration

Sample domain names that 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
app.example.comA or CNAMEAPP Server
s3.example.comadditional A or CNAME record for APP serverAPP Server *required to access S3 emulator URLs like this s3.example.com/bucket *Applicable for 9.0.4+ release only
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)

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

The alternative way is as follows. If you can't use DNS service for any resson, add the records into hosts files on each server and end users' PCs that will use the product:

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

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

192.168.1.1        db.example.com
192.168.1.2        app.example.com
192.168.1.2        s3.example.com
192.168.1.3        apm.example.com
192.168.1.4        ocr.example.com
192.168.1.5        automl.example.com
192.168.1.6        rpa.example.com
192.168.1.7        bi.example.com
← PreviousNext →