All Versions
11
Latest Version
Avg Release Cycle
123 days
Latest Release
295 days ago

Changelog History
Page 1

  • v1.3.2

    May 13, 2020

    ๐Ÿ›  Fixes

    • #72 Issue with new versions of Consul
    • #69 and other spelling mistakes
  • v1.3.1

    March 31, 2020

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed #67.
      ๐Ÿšš The feature added in 1.3.0, reacting to network changes, if name-server auto discovery is enabled, can cause memory issues. Especially if the LookupClient isn't used as singleton. The feature has been removed.
  • v1.3.0

    March 17, 2020

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed a bug with non-empty OPT records, see #51 and #55.
      ๐Ÿ“œ This should fix all those parser errors which were reported by different users using the mongodb C# driver on certain Azure clusters!
    • ๐Ÿ›  Fixed one native path in NameServer.ResolveNameServersNative which did not filter site local addresses properly.

    ๐Ÿ†• New Features

    • ๐Ÿ†• New Configuration API which will replace the property setters on the LookupClient in a future version. The current properties are marked obsolete for now.
      ๐Ÿ‘€ See #33 for more details.
    • โž• Added maximum cache duration setting (#48)
    • ๐Ÿ”ง Auto detect network name server changes (#66). If LookupClient has to discover the NameServers automatically, it now will try to react to changes in the network configuration (especially useful in long running services)
    • ๐Ÿ†• New setting ContinueOnEmptyResponse (#64).
      ๐Ÿ”ง This is enabled per default and instructs LookupClient to query all configured DNS server until the question is answered or no more servers are available.
    • ๐Ÿ‘Œ Improved EDNS handling (#61, #62).
      ๐Ÿ†• New settings to disable or configure the EDNS behavior of LookupClient
    • ๐ŸŒฒ Logging and Tracing and better error handling in general (#60)
    • ๐Ÿ”„ Changed the behavior when LookupClient gets a bad truncated responses, it now tries to re-run the query over TCP if it detects such cases - see #52
    • ๐Ÿ”„ Changed the result of the ResolveService APIs to include weight and order of the SRV records (#34)

    Other Changes

    • โž• Added a lot more unit tests and also tests to validate backward compatibility down to the 1.1.0 API
    • ๐Ÿ”„ Changed the caching mechanism to cache only answered responses.
    • ๐Ÿ”„ Changed caching to not cache by server
  • v1.2.0

    August 16, 2018

    ๐Ÿ†• New Features

    • โž• Added support for SSHFP resource records, see #30, thanks @xudonax!
    • The TTL of cached results will now show the correct (actual) time left in cache. There is a new property, InitialTimeToLive, which stores the original TTL value.

    ๐Ÿ”„ Changes

    • ๐Ÿ‘€ The rules for domain names have been changed in a way that DnsClient will behave more relaxed and not so strict anymore, see #31.
    • ๐Ÿง The name server resolving mechanism to fallback to a native implementation has been re-added. As .NET Core still has issues on e.g. Linux...

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed an issue with very large TCP responses which are split into multiple responses by the server, see #32.
  • v1.1.1

    June 13, 2018

    ๐Ÿ›  Bugfix

    • ๐Ÿ›  Fixes #24, With VS2015 you might have received an error when installing version 1.1.0
  • v1.1.0

    June 04, 2018

    ๐Ÿ’ฅ 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.
  • v1.0.7

    May 01, 2017

    ๐Ÿ†• New Features and Fixes:

    • โž• added more extension methods on IDnsQuery for
      • GetHostName
      • GetHostEntry
        ๐Ÿ‘€ see 63dc01e
    • โž• added extension on IPAddress to get the arpa name of it
    • ๐Ÿ›  fixed spelling of MinimumCacheTimeout... in ILookupClient #5

    ๐Ÿ“š Overall, I added a ton of documentation to the library and published it on dnsclient.michaco.net

  • v1.0.6

    April 27, 2017

    ๐Ÿ›  Fixes issues

    • ๐Ÿง Permission issue with Nameserver resolution on Linux #3
  • v1.0.5

    April 04, 2017

    ๐ŸŽ Mostly bug fixes and performance tuning.

  • v1.0.3

    January 21, 2017

    ๐Ÿ†• New

    • โž• Added synchronous API in addition to the async API.
    • ๐ŸŽ Performance improvements in many areas, especially reuse of UDP sockets and memory allocations
    • โž• Added many new RR types
    • ๐Ÿ‘Œ Improvements for async timeout handling

    ๐Ÿ›  Bugfixes:

    • ๐Ÿ‘ป IPv6 was not correctly supported in 1.0.2 (throwing socket exception).