Configure DNS for ARTESCA

General DNS Setup

Each ARTESCA node must be configured with at least a valid DNS server IP.

Warning

Do not configure more than two DNS servers per ARTESCA node.

ARTESCA is deployed using Ingress Rules which rely on hostnames for routing to applicable services within the cluster. DNS records are required for applications or end users to access those services.

ARTESCA uses a base domain name based on the existing customer DNS domain. For example, if the customer domain name is Example Domain, a subdomain like project.example.com must be chosen and the associated CNAME must be created to resolve Workload Plane (WP) physical IP or WP VIP if any. The bucket S3 service will be accessible on s3.product.example.com.

All following CNAMEs need to resolve to one data IP or a virtual load balancer IP that covers all the data node IPs as described in Configure Data Load Balancer section. Or, if you configured some data virtual IPs, CNAMEs need to resolve to all of those virtual IPs.

The <base-domain-name> will be asked when generating the installation configuration file.

CNAME

Usage

ui.<base-domain-name>

Ingress used to reach the Data Services UI.

iam.<base-domain-name>

Ingress used to reach vault Identity and Access Management for Data Service.

sts.<base-domain-name>

Ingress used to reach vault Security Token Service for Data Service.

management.<base-domain-name>

Ingress used to reach Data Service management API.

s3.<base-domain-name>

Ingress used to reach the Data Service S3 API.

utilization.<base-domain-name>

Ingress used to reach the Scality Utilization Reporting (SUR) API.

crl.<base-domain-name>

Ingress used to reach the Managed CRL Service. This endpoint must be reachable from every endpoint to validate CRL (Certificate Revocation List) when using default certificates generated by ARTESCA.

Note

The base domain name can also be changed after installation.

Refer to the change domain procedure for hardware or software for more information.

Specific DNS Setup

DNS for Single-Node Clusters

For single-node clusters, all entries on the table above must resolve to the cluster workload plane IP.

DNS for Multi-Node Clusters without Load Balancer

For multi-node clusters without load balancer, all entries on the table above must resolve to the cluster workload plane virtual IPs.

DNS for Multi-Node Clusters with Load Balancer

For multi-node clusters with load balancer, all entries on table above must resolve to the load balancer IP.

Check the Configure Data Load Balancer section for more information.

DNS Setup on Windows Server

In case your infrastructure is based on Windows Server, the following section will guide you to configure DNS for ARTESCA.