summaryrefslogtreecommitdiff
path: root/net/py-dnsdiag
AgeCommit message (Collapse)AuthorFilesLines
2022-08-26py-dnsdiag: fix DEPENDS linewiz1-2/+2
2022-08-26py-dnsdiag: update to 2.0.2khorben3-9/+19
Changes in version 2.0.2: * Small bug fixes and improvements Changes in version 2.0.1: * Add support for DNSSEC * Add -F to display flags for each response (dnsping) * Display full response in verbose mode (dnsping) * Add DoT (DNS over TLS) support (dnsping, dnseval) * Add DoH (DNS over HTTPS) support (dnsping, dnseval) * Add TCP support * Improved JSON output support for dnseval * Refactor and PEP8 cleanup * Do not use system resolver when not needed * Add support for user defined source IP address * Add user-specified destination port (-p/--port) * Improve error handling * Display last response code for each entry * Rework custom socket and custom TTL support * Rework time calculation logic to eliminate an extra DNS request that was just sent for timing (dnstraceroute) * Update docs (output samples, use cases, etc) * Use proper terminology (in code) to reduce confusion
2022-01-04*: bump PKGREVISION for egg.mk userswiz1-1/+2
They now have a tool dependency on py-setuptools instead of a DEPENDS
2021-10-26net: Replace RMD160 checksums with BLAKE2s checksumsnia1-2/+2
All checksums have been double-checked against existing RMD160 and SHA512 hashes Not committed (merge conflicts...): net/radsecproxy/distinfo The following distfiles could not be fetched (fetched conditionally?): ./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz ./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch ./net/djbdns/distinfo djbdns-1.05-test28.diff.xz ./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch ./net/djbdns/distinfo djbdns-1.05-multiip.diff ./net/djbdns/distinfo djbdns-cachestats.patch
2021-10-07net: Remove SHA1 hashes for distfilesnia1-2/+1
2020-08-03py-dnsdiag: updated to 1.7.0adam3-15/+16
v1.7.0: Add JSON export Ignore unrelated ICMP messages Fix statistics calculation -c 0 for infinite ping Flush output messages Update sample public resolver data
2018-04-06py-dnsdiag: updated to 1.6.4adam2-8/+8
1.6.4: General improvements and bug fix release
2017-10-05py-dnsdiag: update to 1.6.3adam3-295/+19
1.6.3: Bug fixes.
2016-08-28Remove unnecessary PLIST_SUBST and FILES_SUBST that are now providedwiz1-5/+4
by the infrastructure. Mark a couple more packages as not ready for python-3.x.
2016-06-30Import py-dnsdiag-1.5.0 as net/py-dnsdiag.wiz5-0/+345
Ever been wondering if your ISP is hijacking your DNS traffic? Ever observed any misbehavior with your DNS responses? Ever been redirected to wrong address and suspected something is wrong with your DNS? Here we have a set of tools to perform basic audits on your DNS requests and responses to make sure your DNS is working as you expect. You can measure the response time of any given DNS server for arbitrary requests using dnsping. Just like traditional ping utility, it gives you similar functionality for DNS requests. You can also trace the path your DNS request takes to destination to make sure it is not being redirected or hijacked. This can be done by comparing different DNS queries being sent to the same DNS server using dnstraceroute and observe if there is any difference between the path. dnseval evaluates multiple DNS resolvers and helps you choose the best DNS server for your network. While it is highly recommended to use your own DNS resolver and never trust any third-party DNS server, but in case you need to choose the best DNS forwarder for your network, dnseval lets you compare different DNS servers from performance (latency) and reliability (loss) point of view.