DnsClient.NET v1.1.0 Release Notes

Release Date: 2018-06-04 // about 4 years ago
  • ๐Ÿ’ฅ Breaking Change

    The behavior of this library to resolve name servers changed a little bit.
    ๐Ÿ”ง If you instantiate LookupClient without passing in any name servers, it tries to resolve name servers configured on the network devices.

    ๐Ÿง Previously, some custom native code has been invoked to work around some issues on Linux and UWP.
    Now, this code is basically obsolete and the dotnet core code path will be used.

    In cases where the netstandard 2.x does not work, you'll have to pass in a list of name servers (this affects only platforms where netstandard doesn't work, e.g. UWP is still in progress but should be working in the next netstandard 2.1.
    The native code path is still available via the NameServers object, and can be invoked manually.

    ๐Ÿ†• New Features

    • โž• Added netstandard 2.0 target
    • โž• Added new flags to ContinueOnDnsError and UseRandomNameServer to ILookupClient, see #20
      Important : The defaults for ContinueOnDnsError is True, which means, each query will fall back through all configured name servers if a result contains an error. In previous versions, this fallback did not exist!
      ๐Ÿ”ง The default for UseRandomNameServer is True, which means, on each consecutive query, the client will use a different name server (if multiple are configured). If you want to always use the first one, set this flag to False
    • โž• Added AXFR query type #9

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed #19, an issue with native code resolving host names.