Pool member selection based on DNS entry

It's fine, but realize that you're making a DNS request on EACH new HTTP request. Hopefully the DNS responses are cached between requests, but you're adding some latency nonetheless. I also have to assume that 1) "example.com" is a placeholder for something more dynamic, and 2) you're doing a sort of "reverse forward proxy" here - that is if the requested host name resolves to an IP address then send the traffic there, otherwise send to the default pool.

 

 

If the above assumptions are true, then you may also benefit from a table-based DNS cache mechanism. For example:

 

 

[pseudocode]

 

if table entry doesn't exist for host name {

 

DNS lookup hostname

 

Store DNS response in table

 

Use DNS response

 

} else {

 

Use table entry

 

}

 

[/pseudocode]