Loading

Internal Worker DNS vs Internal DLB DNS in CloudHub

Udgivelsesdato: Jul 25, 2025
Trin

QUESTION

Original question

We also tried calling APIs through the internal worker DNS which did work actually, but we’re not sure about how that would work with an API having two workers i.e. would the internal worker DNS do a round-robin? Would it be able to detect a failure in one of the workers?

So, we would like to know which of the two approaches above is best practice, that is, to call CloudHub APIs from other CloudHub APIs through the internal DLB DNS or internal worker DNS?

Explained

Apps in the same CloudHub VPC can call each other via
  1. Internal worker DNS, refer to How to find my Cloudhub Worker IP Address
  2. Internal DLB DNS, refer to Dedicated Load Balancer public and private IP FAQs
What's the difference and which one is recommended?
 

ANSWER

The internal worker DNS returns workers' IP in a round-robin. The first IP (worker) from the DNS query response is the destination of the request. It relies on the caller app to retry if the previous request fails.   

A DLB tries the next worker if the previous one fails, refer to How does DLB send requests to multiple workers if one of them fails. The benefit of using DLB internal DNS is that it can retry the next worker automatically. 

ADDITIONAL INFORMATION

Vidensartikelnummer

001116315

 
Indlæser
Salesforce Help | Article