SaaSHub helps you find the best software and product alternatives Learn more →
Top 14 dns-client Open-Source Projects
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
massdns
A high-performance DNS stub resolver for bulk lookups and reconnaissance (subdomain enumeration)
-
dnsx
dnsx is a fast and multi-purpose DNS toolkit allow to run multiple DNS queries of your choice with a list of user-supplied resolvers.
-
DnsClient.NET
DnsClient.NET is a simple yet very powerful and high performant open source library for the .NET Framework to do DNS lookups
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
DoNotSend
Sending messages by hacking the DNS protocol. See website for demo server usage instructions
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Project mention: Runs on your OpenWrt box: AdGuard Home is network-wide blocking ads and tracking | news.ycombinator.com | 2024-02-06It works on minimal hardware. I am running it on an Orange Pi 3 LTS.
https://technitium.com/dns/
Seems defeatist to me.
1) There has to be a notion that some things are worth acknowledging as "events"; this leads to the idea that what logs contain is indicators of events. It's a fundamentally philosophical notion. It means you need to take the time to decide what constitutes an event. Hearkening to machine learning and pirates, global warming may inversely correlate with pirates but that doesn't imply causation (either way): you can't just throw statistical techniques at data looking for "hits" and think that's significant. Even if you find some indicator as the article notes it could change; so you should identify some canary indicators and event those as well.
2) Which leads to the point about "bug parts": don't rely on a specific rare indicator, or the failure to identify such an indicator. If you find high-reliability indicators great, but look for other indicators which occur more often, that can be counted, and track those. For instance an indicator that e.g. systemd is restarting /something/, and that's happening more or less frequently, and correlates with a performance observable. If it stops reporting at all, you can start with the presumption that something about logging itself changed.
At this point my philosophical disagreement with centralized logging comes to the fore: it's expensive to load stuff into Splunk. I agree, and that's why I disagree with the approach and prefer federation.
You can use the Totalizer Agent (https://github.com/m3047/rkvdns_examples/tree/main/totalizer...) to increment counters in Redis for regex-identified keys. I don't care whether you use RKVDNS to retrieve the data or something else.
dns-client related posts
-
Hickory DNS
-
You might want async in your project
-
Monitoring your logs is mostly a tarpit
-
Extract cert.pem and privkey.pem from acme.json
-
Announcing `async-dns`
-
Send and Receive Emails in ASP.NET C#
-
natesales/q: A tiny command line DNS client with support for UDP, TCP, DoT, DoH, DoQ and ODoH.
-
A note from our sponsor - SaaSHub
www.saashub.com | 21 May 2024
Index
What are some of the best open-source dns-client projects? This list will help you:
Project | Stars | |
---|---|---|
1 | hickory-dns | 3,635 |
2 | Technitium DNS Server | 3,571 |
3 | massdns | 2,979 |
4 | dnsx | 2,002 |
5 | doggo | 1,541 |
6 | q | 1,511 |
7 | DnsClient.NET | 752 |
8 | routedns | 433 |
9 | DoNotSend | 99 |
10 | dnsclient.nim | 21 |
11 | resolv | 9 |
12 | dns_benchmark | 8 |
13 | resolve | 3 |
14 | rkvdns_examples | 0 |
Sponsored