On 05/12/2025 15:34, Alexander V. Makartsev wrote:
On 05.12.2025 07:24, Max Nikulin wrote:
dig -t SRV _http._srv.deb.debian.org.
This command doesn't return anything useful.
You probably meant it to be:
dig -t SRV _http._tcp.deb.debian.org.
My bad, I am sorry.
$ dig -t SRV _http._tcp.deb.debian.org.
[...]
;; ANSWER SECTION:
_http._tcp.deb.debian.org. 30 IN SRV 10 1 80
debian.map.fastlydns.net.
$ dig -t A debian.map.fastlydns.net.
[...]
debian.map.fastlydns.net. 34 IN A 151.101.194.132
debian.map.fastlydns.net. 34 IN A 151.101.2.132
debian.map.fastlydns.net. 34 IN A 151.101.66.132
debian.map.fastlydns.net. 34 IN A 151.101.130.132
Last-Modified headers for Release files are the same from my location
for ip in \
151.101.194.132 151.101.2.132 151.101.66.132 151.101.130.132; do
curl --resolve "deb.debian.org:80:$ip" -Is -o /dev/null \
-w '%{remote_ip}: %header{last-modified}\n' \
'http://deb.debian.org/debian/dists/trixie/Release';
done
151.101.194.132: Sat, 15 Nov 2025 10:37:37 GMT
151.101.2.132: Sat, 15 Nov 2025 10:37:37 GMT
151.101.66.132: Sat, 15 Nov 2025 10:37:37 GMT
151.101.130.132: Sat, 15 Nov 2025 10:37:37 GMT
I do not see any issue with deb.debian.org.
Is there a chance that other mirror was actually used due to e.g. the
auto-apt-proxy package installed on your machine? Do you have http_proxy
environment set? I would not exclude ISP provider's mirror forced
through a transparent proxy.
By the way, you may specify deb.debian.org in addition to the selected
mirror, so if one mirror is not updated, files may be fetched from
another source.
There was a thread on hiding security updates by serving old files, but
the main repository, unlike security, is not updated frequently enough
require fresh enough files through apt configuration:
Vincent Lefevre. Re: apt config options to specify the CA of the https
repository? Sun, 21 Sep 2025 23:51:17 +0200.
<https://lists.debian.org/msgid-search/[email protected]>
