Confusing about ManagedChannelBuilder.forAddress

I have two grpc client.

1. one use custom nameresolver and priority > DNSNameResolver ManagedChannelBuilder.forTarget("my-resolver:///service")
2. one use default nameresolver. ManagedChannelBuilder.forAddress(ip, port). I expect it will call DNSNameResolver，but in fact, it call custom resolver.

this is ok

ManagedChannel channel = ManagedChannelBuilder.forAddress(ip,port)
                .nameResolverFactory(new DnsNameResolverProvider())
                .build()

ManagedChannel channel = ManagedChannelBuilder.forAddress("dns:///ip:port")
                .build()

It’s very confusing for ManagedChannel.forAddress. The behavior will be changed by register NameResolverProvider.

[voidzcy]

This API use nameResolverFactory.getDefaultScheme() not dns. Sometimes it will call other NameResolver if it priority is higher than dns nameresolver

You are right. forAddress() is one of the oldest APIs of gRPC, before NameResolvers became pluggable. Yes, it uses the scheme of the resolver with the highest priority. This might be a bit surprising and we put some doc on forTarget():

We recommend libraries to specify the schema explicitly if it is known, since libraries cannot know which NameResolver will be default during runtime.

It may surprise users, but not necessarily be broken. We’d also generally recommend using priorities lower than DNS for custom resolvers to preserve the default behavior for forAddress(). But if you know what’s going on, it’s safe to use higher priorities. Anyway, it’s more recommended to use forTarget() with advanced usages such as providing custom resolvers.

[Adol1111]

Yes, of course.Thank you for your help.