Violeta Georgieva

> [@violetagg](https://github.com/violetagg) > > Hello! It seems that the issue has not been progressed, so I would like to ask if it is okay for me to handle it. >...

@erikbeerepoot Something is off here, Reactor Netty 1.1.x uses Reactor Pool 1.0.x. https://github.com/reactor/reactor-netty/blob/1.1.x/gradle.properties Also Reactor Pool 0.2.x reached OSS EOL https://github.com/reactor/.github/blob/main/SUPPORT.adoc#support-timeline

@rethab Without a reproducible example or at least code samples that we can inspect I can comment only this: We handover the buffer to the application: ``` #5: Hint: [4e34b645-1,...

@finalch Reactor Netty version `0.9.7-RELEASE` is not supported. Please update to a supported version: https://github.com/reactor/.github/blob/main/SUPPORT.adoc#support-timeline

@stefan-g When the IP is changed you need to dispose the current connection pool, because it holds open connections to the old IP. You can do it with https://projectreactor.io/docs/netty/release/api/reactor/netty/resources/ConnectionProvider.html#disposeWhen-java.net.SocketAddress-

@stefan-g yes they will

@stefan-g We can think about some configuration but this has to be tightly coupled with DNS resolution configuration. Example let's say there is no expiration of the DNS cache but...

@stefan-g Let me mark this as an enhancement. If you would like to provide a PR for this feature, it would be great!

@samueldlightfoot I cannot find anything that can notify us for the cache expiration, so the only option will be to configure the DNS resolver's cache ttl and the connection pool's...

@samueldlightfoot Another thing that needs attention is that the fact that DNS resolver's cache ttl is reached, doesn't mean that the next result of the DNS resolution will be another...