Load balancing for multiple IPs of a FQDN in dynmic fwding proxy

[Sooryaa-A]

Title: Supporting load balancing for mulitple IPs of a FQDN in dynamic fwd proxy, Similar to strict DNS

Description:
Currently dynamic fwd proxy , dns resolution works similar to LOGICAL DNS, where the very first IP resolved from IP list of an FQDN is getting cached and used for communication.
In a load run case, its like though there are many end points available for a single FQDN, only the same IP will get used, which is not correct.
in our case the number of originators are 1-2 pods, but the serving end has more end points. If two originators are there means only two IP can get used .

[optional Relevant Links:]
I have raised a query regarding this n slack , but didnt get any clarification.
https://envoyproxy.slack.com/archives/C78HA81DH/p1620188772051000?thread_ts=1611234659.004800&cid=C78HA81DH

[antoniovicente]

cc @alyssawilk

It does sound like an useful enhancement.

[alyssawilk]

Yeah right now this is a tricky feature because the upstream host only gets one dns result.
@DavidSchinazi will be landing improvements to DFP soon, to handle multiple addresses serially (for happy eyeballs) and it while I don't think we'll have the cycles to work on doing multiple in parallel, we'll at least do loads of refactoring work to make that work easier. If anyone's up for springboarding off those changes to work on parallel connections we'd be happy to help brainstorm design and do reviews.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[Sooryaa-A]

any update on this?

[Sooryaa-A]

Yeah right now this is a tricky feature because the upstream host only gets one dns result.
@DavidSchinazi will be landing improvements to DFP soon, to handle multiple addresses serially (for happy eyeballs) and it while I don't think we'll have the cycles to work on doing multiple in parallel, we'll at least do loads of refactoring work to make that work easier. If anyone's up for springboarding off those changes to work on parallel connections we'd be happy to help brainstorm design and do reviews.

any brainstorm happening, on how this can be achieved?

[alyssawilk]

I think it's a reasonable feature but someone would have to sign on to do the work :-)

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[DavidSchinazi]

@alyssawilk can you please add the "no stalebot" label to this issue? I think we'll want to keep this issue alive even if we won't address it very soon

[DavidSchinazi]

@Sooryaa-A can you clarify something please? Are you saying you would like DFP to send requests between DNS results round robin, or you saying that you would like to make sure we try multiple DNS results until we find one that works? Thanks!

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.