async-dns does not support:
Additionally, while search domains are supported through configuration, detection of the system configured Search domains is only supported on systems that provide this configuration through a
/etc/resolv.conf file, i.e. it isn’t supported on Windows or OSX, and none of the environment variables that are usually supported on most *nix OSes are supported.
async-dns API is marked as
ApiMayChange as more information is expected to be added to the protocol.
The ability to plugin in a custom DNS implementation is expected to be removed in future versions of Akka. Users should pick one of the built in extensions.
Akka DNS is a pluggable way to interact with DNS. Implementations much implement
akka.io.DnsProvider and provide a configuration block that specifies the implementation via
To select which
DnsProvider to use set
akka.io.dns.resolver to the location of the configuration.
There are currently two implementations:
inet-address- Based on the JDK’s
InetAddress. Using this will be subject to both the JVM’s DNS cache and its built in one.
async-dns- A native implemention of the DNS protocol that does not use any JDK classes or caches.
inet-address is the default implementation as it pre-dates
async-dns will likely become the default in the next major release.
DNS lookups can be done via the
IO(Dns) actor can be interacted with directly. However this exposes the different protocols of the DNS provider.
Dns.Resolved where as the
DnsProtocol.Resolved. The reason for the difference is
async-dns exposes additional information such as SRV records and it wasn’t possible to evolve the original API in a backward compatible way.
The Async DNS provider has the following advantages:
- No JVM DNS caching. It is expected that future versions will expose more caching related information.
- No blocking.
InetAddressresolving is a blocking operation.
To get DNS SRV records
akka.io.dns.resolver must be set to
DnsProtocol.Resolve’s requestType must be set to
DnsProtocol.Resolved will contain