diff --git a/docs/advanced-usage.md b/docs/advanced-usage.md
index 23c3528de4..19e8c2b9d5 100644
--- a/docs/advanced-usage.md
+++ b/docs/advanced-usage.md
@@ -207,7 +207,7 @@ disabled by setting commandLatencyPublisherOptions(…)
to
DnsResolvers.JVM_DEFAULT ( or netty if present)
Since: 3.5, 4.2
+Since: 3.5, 4.2. Deprecated: 6.4
Configures a DNS resolver to resolve hostnames to a
java.net.InetAddress
. Defaults to the JVM DNS resolution
that uses blocking hostname resolution and caching of lookup results.
@@ -223,6 +223,34 @@ netty's AddressResolver
that resolves DNS names on
Bootstrap.connect()
(requires netty 4.1)
addressResolverGroup
DefaultAddressResolverGroup.INSTANCE ( or netty DnsAddressResolverGroup if present)
Since: 6.1
+Sets the AddressResolverGroup
for DNS resolution. This option is only effective if
+DnsResolvers#UNRESOLVED
is used as DnsResolver
. Defaults to
+io.netty.resolver.DefaultAddressResolverGroup#INSTANCE
if netty-dns-resolver
+is not available, otherwise defaults to io.netty.resolver.dns.DnsAddressResolverGroup
Users of DNS-based Redis-HA setups (e.g. AWS ElastiCache) might want to configure a different DNS +resolver group. For example: + +```java +new DnsAddressResolverGroup( + new DnsNameResolverBuilder(dnsEventLoop) + .channelType(NioDatagramChannel.class) + .resolveCache(NoopDnsCache.INSTANCE) + .cnameCache(NoopDnsCnameCache.INSTANCE) + .authoritativeDnsServerCache(NoopAuthoritativeDnsServerCache.INSTANCE) + .consolidateCacheSize(0) +); +``` + +
+reconnectDelay
Delay.exponential()