Or, more accurately, doesn't handle failed axfers terribly well. If one of the name servers for a domain refuses axfers dlint will not try the other servers for a domain, meaning that a zone that could otherwise be at least somewhat linted can go completely unchecked. If consistency checking is desired then it would always be possible to fall back on looking up individual records. At the present moment the domain ed.aculab.com has a configuration which shows this, though this may change. It also fails to detect the cause of the error (it reports no A records rather than reporting that the axfer was denied).
Hello!
Unfortunately this is a short status update only.
I have been unable to reach the upstream author for
some time now. Homepage is down and I don't get any answers
to my mails.
Any help appreciated.
I'd like to have a look at that bugs by myself, but I
might have time to do this next week at the best.
I'd highly appreciate patches or any other help here, too.
Regards
Florian
Hello Paul!
This is one of the bugreports I mentioned.
Regards
Florian
-----FW: <20011105023228.CE352E71A@cassiel.sirena.org.uk>-----
Date: Mon, 05 Nov 2001 02:32:28 +0000
From: Mark Brown <broonie@sirena.org.uk>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#118309: dlint: Doesn't try all NSes
Package: dlint
Version: 1.4.0-2
Severity: normal
Or, more accurately, doesn't handle failed axfers terribly well. If one
of the name servers for a domain refuses axfers dlint will not try the
other servers for a domain, meaning that a zone that could otherwise be
at least somewhat linted can go completely unchecked. If consistency
checking is desired then it would always be possible to fall back on
looking up individual records. At the present moment the domain
ed.aculab.com has a configuration which shows this, though this may
change.
It also fails to detect the cause of the error (it reports no A records
rather than reporting that the axfer was denied).
--------------End of forwarded message-------------------------