NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #128 most downloaded on NuGet
DnsClient.NET is a simple yet very powerful and high performance open source library for the .NET Framework to do DNS lookups
Latest stable
1.8.0
Last release 2 years ago
no release in 18 months
Release timing varies
gaps range from 8 days to 1.7 years
Nearly every release is documented
notes for 18 of 20 stable releases
1 version withdrawn
withdrawn after publishing
127 years old
28 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
[Breaking Change] Removed obsolete LookupClient configuration properties by @MichaCo in #221
Full Changelog: 1.7.0...1.8.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This is a small release without huge changes.
See #162 . Fixed errors with the windows registry nuget, which is used in just an edge case scenario at startup, causing all kinds of problems 😑
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 handli
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
IsOSPlatform(OSPlatform.Windows). Seems that was not enough. See #133Several changes to name server auto resolution see #122 for the announcement
Details: See https://github.com/MichaCo/DnsClient.NET/milestone/9?closed=1
Support for parsing TLSA, RRSig, DS, NSEC, DnsKey and SPF records (PRs #71 , #86 , #87 )
Fixes #72 Issue with new versions of Consul #69 and other spelling mistakes
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
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 mon
NameServer.ResolveNameServersNative which did not filter site local addresses properly.LookupClient in a future version. The current properties are marked obsolete for now.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)ContinueOnEmptyResponse (#64).LookupClient to query all configured DNS server until the question is answered or no more servers are available.LookupClientLookupClient gets a bad truncated responses, it now tries to re-run the query over TCP if it detects such cases - see #52ResolveService APIs to include weight and order of the SRV records (#34)Added support for SSHFP resource records, see #30 , thanks @xudonax !
InitialTimeToLive, which stores the original TTL value.Fixes #24, With VS2015 you might have received an error when installing version 1.1.0
The behavior of this library to resolve name servers changed a little bit. If you instantiate LookupClient without passing in any name servers, it tri
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.
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 FalseBug Fixes
added more extension methods on IDnsQuery for
IDnsQuery for
IPAddress to get the arpa name of itILookupClient #5Overall, I added a ton of documentation to the library and published it on dnsclient.michaco.net
Permission issue with Nameserver resolution on Linux #3
Fixes issues
Mostly bug fixes and performance tuning.
Mostly bug fixes and performance tuning.
Nothing published for this version
Added synchronous API in addition to the async API.
New
Bugfixes:
Nothing published for this version
Nothing published for this version
Better xplat support for determining DNS Servers as the .NET Framework has some bugs and lacking some features in this regards.
Nothing published for this version
Nothing published for this version
The most basic features implemented with fully managed Udp and Tcp client.
The most basic features implemented with fully managed Udp and Tcp client.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.