Releases: MichaCo/DnsClient.NET
Releases · MichaCo/DnsClient.NET
1.8.0
What's Changed
- Dropping netstandard1.3, net45 and net5.0 target. by @MichaCo in #206
- Add CERT resource record support by @JoeShook in #203
- Reduce allocations by @antonfirsov in #216
- ArgumentOutOfRangeException on payloads above 4096bytes by @MichaCo in #217
- Thread safe ID generation by @antonfirsov in #218
- [Breaking Change] Removed obsolete LookupClient configuration properties by @MichaCo in #221
- Fixing string format, see #227 by @MichaCo in #228
- Reflection-free compatibility changes by @RatherLogical in #214
New Contributors
- @JoeShook made their first contribution in #203
- @antonfirsov made their first contribution in #216
- @RatherLogical made their first contribution in #214
Full Changelog: 1.7.0...1.8.0
1.7.0
1.6.1
1.6.0
New / Change
In 1.5, the DNS response ID validation was lifted to just log warnings.
This mechanic has been reverted to throw an error but with a bit better handling and retrying the request thanks to @JamesKovacs. See #140
Bug Fixes
- Until this version, UDP sockets were reused in favor of performance. That did cause some issues though and all kind of pooling has been removed. See #132
- See #136, removed a case where the response was null and might have caused some errors in some cases
- When run in Azure Functions, the Name Resolution policy feature we added in 1.5 threw a Platform not Supported exception, although we did check for
IsOSPlatform(OSPlatform.Windows)
. Seems that was not enough. See #133
1.5.0
New
- Several changes to name server auto resolution
see #122 for the announcement- DnsClient now also respects NRPT policies (a Windows only feature), see #114 and thanks to @SteveSyfuhs
- Added DNS suffix #113
- Added NAPTR records support, thanks to @rj2Skipper see #88
- Also added more DNS Sec records: NSec3, NSec3Param see #119
Bugfixes
Details: See https://github.com/MichaCo/DnsClient.NET/milestone/9?closed=1
1.4.0
New
- Support for parsing TLSA, RRSig, DS, NSEC, DnsKey and SPF records (PRs #71, #86, #87)
- New configuration option to allow the client to cache failed responses (this is opt-in, default is no cache), see #80
- Updated System.Buffers reference to the latest version (from 4.4.0 to 4.5.1)
- The request and response Id check is now a warning log instead of a hard error, see #74
(still investigating if there is an actual issue under Linux with async socket usage....)
Bugfixes
1.3.2
1.3.1
1.3.0
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
1.2.0
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.