Home > Storage > ObjectScale and ECS > Product Documentation > ECS with HAProxy Load Balancer > Domain name system (DNS)
In this example, a DNS is setup on a Windows server and accessible from the server hosting HAProxy. Table 2 shows the DNS entries created. Adding DNS entries allows mapping of “names” to IP addresses. In this example, DNS is used as a mechanism for translating the object protocol (S3, Atmos, or Swift) the client is using and allows HAProxy to direct request to the appropriate pool of ECS nodes based on protocol name.
The advantage of this approach is that HAProxy runs all three protocols on the standard HTTP port 80. The names associated with each object protocol will be mapped to one IP address associated with the HAProxy and translate it to a pool of ECS nodes. An “A-record “ is created in DNS which maps a name to the IP address of HAProxy and CNAME provides an alias for each protocol.
DNS record | Record type | Record data | Comments |
os.ecstme.org | A | 10.246.150.199 | HAProxy external IP Address and also used for S3 protocol access (os=object store) |
*.os.ecstme.org | CNAME | os.ecstme.org | Used for S3 virtually hosted buckets, i.e., mybucket.os.ecstme.org |
atmos.ecstme.org | CNAME | os.ecstme.org | Endpoint for clients using the Atmos |
swift.ecstme.org | CNAME | os.ecstme.org | Endpoint for clients using the Swift protocol |
From the Windows Server, start up the DNS Manager and add DNS entries of “New Host” for A-Record and “New Alias” in your domain zone as described in Table 2. Sample screenshots of this are shown in the following two figures.