Your message dated Sun, 22 Oct 2017 13:19:11 +0200
with message-id 
<1508671151.815349.1146906880.773a8...@webmail.messagingengine.com>
and subject line Closing bugs in old-old-stable bind9 versions
has caused the Debian Bug report #260915,
regarding Sarge errors - DNS resolver
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 [email protected]
immediately.)


-- 
260915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=260915
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: Bind
Version: 9 - sarge

I've installed Sarge yesterday from 'netinstall' and have got
strange errors with ip address resolver and generaly with the
'net.

I've  done for example 'ping ftp.icm.edu.pl' and durring the
'ping' it itself changed the pinged adress:

64 bytes from ftp.icm.edu.pl (193.219.28.2): icmp_seq=296
ttl=246 time=61.6 ms
64 bytes from ftp.icm.edu.pl (193.219.28.2): icmp_seq=297
ttl=246 time=64.5 ms
64 bytes from ftp.icm.edu.pl (193.219.28.2): icmp_seq=298
ttl=246 time=54.0 ms
64 bytes from ftp.icm.edu.pl (193.219.28.2): icmp_seq=299
ttl=246 time=58.4 ms
64 bytes from security.debian.org (193.219.28.2): icmp_seq=300
ttl=246 time=55.6 ms
64 bytes from security.debian.org (193.219.28.2): icmp_seq=301
ttl=246 time=58.1 ms
64 bytes from security.debian.org (193.219.28.2): icmp_seq=302
ttl=246 time=51.4 ms

Problem is that security.debian.org ought to be 194.109.137.218
while ftp.icm.edu.pl is in fact 193.219.28.2

The only excuse might be that on the second connection I was
using dselect and apt-get and after initial success have got
error in download from my main download server which is
ftp.icm.edu.pl...

IBM335:/etc/apt# apt-get update
0% [Connecting to ftp.icm.edu.pl (1.0.0.0)]
IBM335:/etc/apt# apt-get update
Err ftp://ftp.icm.edu.pl testing/main Packages
  Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Err ftp://ftp.icm.edu.pl testing/main Release
  Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Err ftp://ftp.icm.edu.pl testing/main Sources
  Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Err ftp://ftp.icm.edu.pl testing/main Release
  Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Failed to fetch
ftp://ftp.icm.edu.pl/pub/Linux/debian/dists/testing/main/binary-i386/Packages.gz
 
Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Failed to fetch
ftp://ftp.icm.edu.pl/pub/Linux/debian/dists/testing/main/binary-i386/Release 
Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Failed to fetch
ftp://ftp.icm.edu.pl/pub/Linux/debian/dists/testing/main/source/Sources.gz 
Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Failed to fetch
ftp://ftp.icm.edu.pl/pub/Linux/debian/dists/testing/main/source/Release 
Could not connect to ftp.icm.edu.pl:21 (1.0.0.0), connection
timed out
Reading Package Lists... Done
E: Some index files failed to download, they have been ignored,
or old ones used instead.


I think something is wrong with resolver...
yours
WD


--- End Message ---
--- Begin Message ---
Version: 1:9.10.3.dfsg.P4-12.3

Hi,

the bind9 bug list grew too much and the Debian BIND team cannot
simply test all the reported bugs against versions not in stable, so
this is mass bug close, as either the version is no longer relevant
(because of old-old-stable 9.8.x or old-stable 9.9.5 or even older
version of bind9) or the bug was already fixed.

However, if you can reproduce the bug with a current version in stable,
please use Debian BTS 'found <bug> <version_you_reproduced_the_issue>'
command to retag the bug and reopen it.

Cheers,
Ondrej

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to