Dev1 Galaxy Forum / [SOLVED] Some problem with deb.devuan.org

Re: [SOLVED] Some problem with deb.devuan.org

dummy@example.com (onefang) — Wed, 22 Feb 2023 16:22:58 +0000

I'm not seeing those issues. Might be local DNS issues at your end.

Though while I was logging in to say that, got solved.

Re: [SOLVED] Some problem with deb.devuan.org

dummy@example.com (serq) — Wed, 22 Feb 2023 16:17:15 +0000

boughtonp, Thank you helped

Re: [SOLVED] Some problem with deb.devuan.org

dummy@example.com (boughtonp) — Wed, 22 Feb 2023 16:11:29 +0000

It is generally helpful to identify the command being run - is it apt?

However, I think I'm seeing the same/similar - a ping/traceroute/curl to deb.devuan.org all have a ~60 second delay before responding, which to me suggests a DNS timeout.

Running dig deb.devuan.org returns immediately, and reveals a CNAME to deb.rr.devuan.org (which has multiple A records), but deb.rr.devuan.org itself is responding to ping/traceroute/curl without delay.

If I force IPv4 (e.g. ping -4 deb.devuan.org) then I get an immediate response, whilst forcing IPv6 is eventually timing out with a "Could not resolve host" error.

So, the issue would seem to be that there's no IPv6 AAAA records at deb.rr.devuan.org, and something doesn't like that.

I assume enabling Apt's Acquire::ForceIPv4 option will get around this, i.e. via /etc/apt/apt.conf.d or using apt -o Acquire::ForceIPv4=true update.

[SOLVED] Some problem with deb.devuan.org

dummy@example.com (serq) — Wed, 22 Feb 2023 15:20:03 +0000

Hi All,
0% [Connection with deb.devuan.org]
And a very long expectation before what begins to happen. Is it temporary?