[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#824670: marked as done (ITP: dnsdiag -- DNS Diagnostics and Performance)

Your message dated Wed, 01 Feb 2017 10:00:11 +0000
with message-id <E1cYrhz-0007ku-No@fasolo.debian.org>
and subject line Bug#824670: fixed in dnsdiag 1.4.0-1
has caused the Debian Bug report #824670,
regarding ITP: dnsdiag -- DNS Diagnostics and Performance
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
824670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824670
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist

* Package name    : dnsdiag
  Version         : 1.3.4
  Upstream Author : Babak Farrokhi <babak@farrokhi.net>
* URL             : https://dnsdiag.org/
* License         : 2-clause BSD
  Programming Lang: Python
  Description     : DNS Diagnostics and Performance Measurement Tools

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.

----

Similar to SMTP ping, this tool can also be used to run network
diagnostics in restricted environment. It can also be used to detect
DNS hijacking and tampering.

I also hope it can eventually replace commercial tools like DNSstuff
or intodns.com:

https://github.com/farrokhi/dnsdiag/issues/16

It has all the components to build such a tool already factored in.

Speaking of which, dnsdiag has two dependencies that could be an issue
in Debian. It depends on python-dnspython which is packaged already,
but dnstraceroute requires a modification to the code. It is unclear
for now which exactly are the modifications required, so I asked
upstream for clarification in that regard:

https://github.com/farrokhi/dnsdiag/issues/17

The other bit of the puzzle is the "cymruwhois" package. It seems it
is only used to do IP to ASN lookups:

https://github.com/farrokhi/dnsdiag/blob/b2dab7affcb9a535bbf0e9f7bb4cac5d330a6368/dnstraceroute.py#L86

Yet the current python-whois package in Debian doesn't support that:

>>> import whois
>>> domain = whois.query('199.58.80.1')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/whois/__init__.py", line 47, in query
    if tld not in TLD_RE.keys(): raise Exception('Unknown TLD: %s\n(all known TLD: %s)' % (tld, list(TLD_RE.keys())))
Exception: Unknown TLD: 1
(all known TLD: ['biz', 'org', 'name', 'me', 'at', 'us', 'de', 'co', 'jp', 'lv', 'ru', 'be', 'net', 'co_jp', 'uk', 'eu', 'nz', 'com', 'fr', 'it', 'info', 'pl', 'cz'])

... so it would seem that library would need to be packaged
separately.

The thing is on pipy so it should be fairly simple to ship:

https://pypi.python.org/pypi/cymruwhois

however, the releases on pypi are out of date because the author can't
seem to ship new packages there:

https://github.com/JustinAzoff/python-cymruwhois/issues/4

so care should be taken in using the github packages (1.5+), and not
the pypi ones:

https://github.com/JustinAzoff/python-cymruwhois/releases

--- End Message ---
--- Begin Message --- 
Source: dnsdiag
Source-Version: 1.4.0-1

We believe that the bug you reported is fixed in the latest version of
dnsdiag, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 824670@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ana Custura <ana@netstat.org.uk> (supplier of updated dnsdiag package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 20:47:30 +0000
Source: dnsdiag
Binary: dnsdiag
Architecture: source all
Version: 1.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ana Custura <ana@netstat.org.uk>
Changed-By: Ana Custura <ana@netstat.org.uk>
Description:
 dnsdiag    - DNS request auditing toolset
Closes: 824670
Changes:
 dnsdiag (1.4.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #824670)
Checksums-Sha1:
 b920e6418d3d7903985ce436ffe5923d96267f09 1867 dnsdiag_1.4.0-1.dsc
 b71c04afb6c8ccd161a6dbc6713e890669d46bf3 11115 dnsdiag_1.4.0.orig.tar.gz
 edb8847a95fe4a4f731bf29c88e55519bf8bd6b0 4320 dnsdiag_1.4.0-1.debian.tar.xz
 a96636192ba02bb1b771edd76aa597603a53738a 11284 dnsdiag_1.4.0-1_all.deb
 5cfa4bb58b5410baad172d2232cd083df67aeed4 4844 dnsdiag_1.4.0-1_amd64.buildinfo
Checksums-Sha256:
 b1dc2b2266a1d7b764e0dea861ea4a990d47204b7c596148166b40fde30adc4c 1867 dnsdiag_1.4.0-1.dsc
 a282cb45b8e7a7c6e1f2ca3f25cbefa5dc975c1d13459f19c8b2efe5daa66aac 11115 dnsdiag_1.4.0.orig.tar.gz
 7a432c68c7d101d98b8a79b401fc4ae3202f4f7520e8f4971c61c9a2db52d4e9 4320 dnsdiag_1.4.0-1.debian.tar.xz
 513dbb0d4f92f6bd523b62e49106af5d04ebffe3dce3a5c52921883e087b4c95 11284 dnsdiag_1.4.0-1_all.deb
 00b9b9b255fc17fb7fae27ca6ad96fdb62f3fc6b25c1654373d7053dfa478472 4844 dnsdiag_1.4.0-1_amd64.buildinfo
Files:
 c84a49144905bc7c3a6e96eca93c35fa 1867 net optional dnsdiag_1.4.0-1.dsc
 f375f085cf9561e9d3f3b587f891b2b2 11115 net optional dnsdiag_1.4.0.orig.tar.gz
 d7fc346a4f99d8152df69b5d87e8fa6b 4320 net optional dnsdiag_1.4.0-1.debian.tar.xz
 35b9883f03329c618157800e5fbabc22 11284 net optional dnsdiag_1.4.0-1_all.deb
 1d02d14140172ea161e46871f88ceeb4 4844 net optional dnsdiag_1.4.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEjckBzmQUbASK1Q+7eSFSUnt1kh4FAliRGLEACgkQeSFSUnt1
kh7LrQ/+J9B2qw9kiVRteltMPIdako+DAoAJLUx3N0qCJujTuhUslfxx8/w44EWE
c75tmEo/3FDr2Psm4iHlDIIPSLLhLXer3W3EeBpXqx3ng46kXjUOsQtW8rubwMLz
HU0ShsA3Q+y2BnTP7cqy6Gc2M4JNwA+TE/DjXPN+tCcrqwJQtN+UnlgNNLs9+31R
czsy1Y5NOyG4sLBldWopyYoSh73SWCkyk8X++4XaJIwbd+GXrfbWhGkm0wcmgmE5
YdDpMXx2aFaSrzL8dYh+qzQVd9xa8yFGbPkwKMv8b8pxgCjKspHlGvfa90BBUKLE
y+MzNeSHRUuhVA048WvN6qf4DDr5dUGrhrOd1bDR1lwUuDprf/BaBePzfrtAB/l6
RQh2kHGu4bth7EwokEtb7PHaEqPZPWv92ke48lYSNxRaNjeGK+zON3rmnTqUt0AO
R5ed+X2RBhyLoMRaBhd47q9GuBbbw6Z24aFZAkO6CiQT6FeLOc+W7HltSto0BWje
nk5X9VYtQH8PJHq/1Gx/1imhhab9e6BLTY01ZATwJDHtVJC596Qz6GiIvqPb3w0r
cLzxODT0difte1rPzumFDDj+juRCbXH/beBOjj82G/oUdWJSlj2MVlAbFiBy703t
j1DznA7vxWaoNYpbmmk5PDh4SHweU/+ongr7jmNCFkMetwEJoRY=
=ccEB
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: