Uses of Interface
io.netty.resolver.dns.DnsQueryLifecycleObserver
Packages that use DnsQueryLifecycleObserver
Package
Description
An alternative to Java's built-in domain name lookup mechanism that resolves a domain name asynchronously,
which supports the queries of an arbitrary DNS record type as well.
-
Uses of DnsQueryLifecycleObserver in io.netty.resolver.dns
Classes in io.netty.resolver.dns that implement DnsQueryLifecycleObserverModifier and TypeClassDescriptionfinal classCombines twoDnsQueryLifecycleObserverinto a singleDnsQueryLifecycleObserver.Methods in io.netty.resolver.dns that return DnsQueryLifecycleObserverModifier and TypeMethodDescriptionBiDnsQueryLifecycleObserverFactory.newDnsQueryLifecycleObserver(DnsQuestion question) DnsQueryLifecycleObserverFactory.newDnsQueryLifecycleObserver(DnsQuestion question) Create a new instance of aDnsQueryLifecycleObserver.LoggingDnsQueryLifeCycleObserverFactory.newDnsQueryLifecycleObserver(DnsQuestion question) NoopDnsQueryLifecycleObserverFactory.newDnsQueryLifecycleObserver(DnsQuestion question) BiDnsQueryLifecycleObserver.queryCNAMEd(DnsQuestion cnameQuestion) DnsQueryLifecycleObserver.queryCNAMEd(DnsQuestion cnameQuestion) The query returned a CNAME which we may attempt to follow with a new query.BiDnsQueryLifecycleObserver.queryNoAnswer(DnsResponseCode code) DnsQueryLifecycleObserver.queryNoAnswer(DnsResponseCode code) The response to the query didn't provide the expected response code, but it didn't returnDnsResponseCode.NXDOMAINso we may try to query again.BiDnsQueryLifecycleObserver.queryRedirected(List<InetSocketAddress> nameServers) DnsQueryLifecycleObserver.queryRedirected(List<InetSocketAddress> nameServers) The query has been redirected to another list of DNS servers.Constructors in io.netty.resolver.dns with parameters of type DnsQueryLifecycleObserverModifierConstructorDescriptionCreate a new instance.