|
May
27 |
|
comment |
Possible to force the client to try the next A record after PHP interpreter starts? thanks for the input, but I'm not talking about load balancing here. Round robin DNS can certainly be used as a simplistic approach to load balancing (albeit without any pertinent load information, most of the time), but that's tertiary to the question. |
|
May
27 |
|
comment |
Possible to force the client to try the next A record after PHP interpreter starts? I am referring to the situation in which multiple A records are configured for a site, in which case multiple IP addresses are returned to the client, not just one as indicated above. Also, I did not make any mention of load balancing in the question. That said, if the rest of the response is correct, this seems to confirm my suspicion that skipping the current A record is not possible post-connection. |
|
May
27 |
|
comment |
Possible to force the client to try the next A record after PHP interpreter starts? @Baba if my understanding is correct, the load balancer is also unaware of the A record sorting... It just distributes incoming traffic across the nodes in its cluster. |
|
May
27 |
|
asked | Possible to force the client to try the next A record after PHP interpreter starts? |
|
Apr
27 |
|
awarded | Enlightened |
|
Oct
23 |
|
awarded | Guru |
|
Jul
22 |
|
awarded | Good Answer |
|
Jul
5 |
|
awarded | Yearling |
|
Jan
5 |
|
awarded | Nice Answer |
|
Aug
1 |
|
awarded | Teacher |
|
Aug
1 |
|
answered | css transform, jagged edges in chrome |
|
Jul
5 |
|
asked | Multiple mixed-value rows in MySQL IN comparison with subquery |
