I am running a node.js cluster on a host. Multiple processes start, each listening on a different port. I would like to take advantage of dynamic configuration using SRV records but I seem to have HAProxy discovering only one backend per IP address. Is having multiple backends on an IP address a …

[image] KrisM: I am running a node.js cluster on a host. Multiple processes start, each listening on a different port. I would like to take advantage of dynamic configuration using SRV records but I seem to have HAProxy discovering only one backend per IP address. Is having multiple backends …

Assuming only one server per IP address is currently permitted, is this expected to be the case permanently? Trying to validate whether or not my use case is valid (multiple backends on the same IP). Thanks.

Hi Lukas, You’re absolutely right! We implemented a “deducplication” detection… That said, this use case sound reasonable but I think the implementation won’t be tricky…

[image] Baptiste: That said, this use case sound reasonable I just want to point out that the use case is super common if you use a cluster scheduler like nomad: once you have more than two instances of a job, it can happen that two of them run on the same host and jobs on one host share one …

Hi. We’re also affected by this after an upgrade from 1.5 to 1.8 and using the Resolvers functionality. I’m really glad this was posted else I would’ve been debugging for ages haha. In terms of the fix is there somewhere where this is being tracked? Or where would be the best place for me to kee…

Hi @Baptiste . Apologies for tagging you but I was wondering if there was any further progress made on this or if there was a better place for me to check for updates? We’re currently blocked from upgrading to 1.8 due to this. Although we’re using standard hostname resolution and not SRVs, it’s th…

sadly this is still an issue in 1.8.15, the DSN SRV support is essentially broken if you are using containers as it’s very common to run more than one container per host :frowning:

@hampsterx This was implemented in 1.8.14 and you can enable the behavior with resolve-opts allow-dup-ip, also see resolve-opts docs.

Using SRV Record - multiple entries per IP gets "No IP for server"

Help!

scarey February 7, 2018, 5:57pm 4

I second that use case.

1.8.x Resolvers not working when multiple backend servers share the same hostname \ IP?

Topic		Replies	Views
1.8.x Resolvers not working when multiple backend servers share the same hostname \ IP? Help!	35	6040	October 16, 2018
Trouble with DNS Resolvers sticking to single IP address Help!	30	24863	May 19, 2022
Using SRV Record - number of records in DNS not limiting server-template count Help!	1	1002	February 7, 2018
HAProxy 1 IP for multiple website on diffrent domain Help!	3	1630	February 12, 2019
HAProxy 2.0.5 often fails to quickly update SRV records Help!	8	1109	October 13, 2020

Using SRV Record - multiple entries per IP gets "No IP for server"

Related topics