DnsClient.NET alternatives and similar packages
Based on the "Protocols" category.
Alternatively, view DnsClient.NET alternatives based on common mentions on social networks and blogs.
8.8 4.5 L3 DnsClient.NET VS SSH.NETSSH.NET is a Secure Shell (SSH) library for .NET, optimized for parallelism.
8.2 9.7 L1 DnsClient.NET VS FluentFTPAn FTP and FTPS client for .NET & .NET Standard, optimized for speed. Provides extensive FTP commands, File uploads/downloads, SSL/TLS connections, Automatic directory listing parsing, File hashing/checksums, File permissions/CHMOD, FTP proxies, FXP support, UTF-8 support, Async/await support, Powershell support and more. Written entirely in C#.
6.7 0.0 DnsClient.NET VS NModbus4NModbus4 is a C# implementation of the Modbus protocol. This project is archived in favor of https://github.com/NModbus/NModbus
A C# cross platform connected device framework
Really Simple Service Discovery Protocol - a 100% .Net implementation of the SSDP protocol for publishing custom/basic devices, and discovering all device types on a network.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of DnsClient.NET or a related project?
DnsClient.NET is a simple yet very powerful and high performance open source library for the .NET Framework to do DNS lookups.
See http://dnsclient.michaco.net for more details and documentation.
The following example instantiates a new
LookupClient to query some IP address.
var lookup = new LookupClient(); var result = await lookup.QueryAsync("google.com", QueryType.A); var record = result.Answers.ARecords().FirstOrDefault(); var ip = record?.Address;
- Sync & Async API
- UDP and TCP lookup, configurable if TCP should be used as fallback in case the UDP result is truncated (default=true).
- Configurable EDNS support to change the default UDP buffer size and request security relevant records
- Query result cache based on provided TTL
- Minimum TTL setting to overrule the result's TTL and always cache the responses for at least that time. (Even very low value, like a few milliseconds, do make a huge difference if used in high traffic low latency scenarios)
- Maximum TTL to limit cache duration
- Cache can be disabled
- Multiple DNS endpoints can be configured. DnsClient will use them in random or sequential order (configurable), with re-tries.
- Configurable retry of queries
- Optional audit trail of each response and exception
- Configurable error handling. Throwing DNS errors, like
NotExistentDomainis turned off by default
- Optional Trace/Logging
Supported resource records
- A, AAAA, NS, CNAME, SOA, MB, MG, MR, WKS, HINFO, MINFO, MX, RP, TXT, AFSDB, URI, CAA, NULL, SSHFP, TLSA, RRSIG, NSEC, DNSKEY, DS
- PTR for reverse lookups
- SRV for service discovery.
LookupClienthas some extensions to help with that.
- AXFR zone transfer (as per spec, LookupClient has to be set to TCP mode only for this type. Also, the result depends on if the DNS server trusts your current connection)
Build from Source
The solution requires a .NET Core 3.x SDK and the .NET 4.7.1 Dev Pack being installed.
Just clone the repository and open the solution in Visual Studio 2017/2019.
The unit tests don't require any additional setup right now.
If you want to test the different record types, there are config files for Bind under tools. Just download Bind for Windows and copy the binaries to tools/BIND, then run bind.cmd. If you are running this on Linux, you can use my config files and replace the default ones if you want.
Now, you can use samples/MiniDig to query the local DNS server. The following should return many different resource records:
dotnet run -s localhost mcnet.com any