MRmrngm·Nov 19, 2025
https://github.com/farrokhi/dnsdiag is another great toolbox for looking into DNS problems.
In Show HN: DNS Benchmark Tool – Compare and monitor resolversfarrokhi
dnsdiag
Python2017–2025
farrokhi / dnsdiag
dnsdiag
DNS Measurement, Troubleshooting and Security Auditing Toolset
2Distinct people
2Mentions
0Explicit recommenders
1.1KGitHub stars
What to know before exploring
What it is
DNS Measurement, Troubleshooting and Security Auditing Toolset
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year2 dated mentions
Observed mentions: 2017-11-17 12:00:45 UTC to 2025-11-19 18:50:41 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesThe response time depends on network peering from their anycast locations. I am seeing different response times based on test locations.
From US:
# ./dnseval.py -f google-vs-quad9.txt -c 50 -C yahoo.com
server avg(ms) min(ms) max(ms) stddev(ms) lost(%) ttl flags
----------------------------------------------------------------------------------------------------
8.8.8.8 31.857 31.278 33.416 0.434 %0 1332 QR -- -- RD RA -- --
8.8.4.4 31.865 31.361 32.872 0.336 %0 1330 QR -- -- RD RA -- --
9.9.9.9 93.703 92.797 95.362 0.586 %0 1391 QR -- -- RD RA -- --
From Iran:
# ./dnseval.py -f google-vs-quad9.txt -c 50 -C yahoo.com
server avg(ms) min(ms) max(ms) stddev(ms) lost(%) ttl
Read the rest
flags
----------------------------------------------------------------------------------------------------
8.8.8.8 105.093 90.046 130.871 9.749 %0 3590 QR -- -- RD RA -- --
8.8.4.4 99.458 84.472 133.375 11.308 %0 3585 QR -- -- RD RA -- --
9.9.9.9 96.231 83.957 134.709 9.503 %0 3595 QR -- -- RD RA -- --
Tests are performed using dnsdiag tools: https://github.com/farrokhi/dnsdiag