DnsClient.NET v1.3.0 Release Notes
Release Date: 2020-03-17 // about 4 years ago-
๐ 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 instructsLookupClient
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 ofLookupClient
- ๐ฒ 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
- ๐ Fixed a bug with non-empty OPT records, see #51 and #55.