Once your container has been deployed and at least one application assigned, the next step is to route traffic to it.
If traffic reaches the container directly from the outside your organization, you can configure a DNS A record to route IPv4 traffic to the correct IP address. We do not currently support IPv6.
In most cases traffic will reach the container from elsewhere in your infrastructure. You will need to route that traffic to the correct internal IP address and port. This container configuration can be found on the Servers page for each application in your container. Port mapping can be found here.
If using a load balancer, ADC or other service, multiple DNS records can be pointed to the same public IP address. Meaning it can handle traffic for the hostnames (domains) across all the applications within your container.