Unable to update Fedora, dnf displaying curl time outs and DNS errors likely because of DC move

Ask Fedora
1

I and others, are unable to update Fedora since the process of the data center move began.

When I update using dnf, it displays curl time out errors for mirrors.fedoraproject.org and someone I know, is instead getting errors that the same hostname cannot be resolved.

I can’t speak for the other person’s DNS errors, but the Fedora Status page on the move indicates end-user services would not be affected. We’ve both been seeing these errors since 30 June.

If the move is going to prevent users from updating their systems, then the status site info should reflect this.

2

DNF works for me.

What does DNS resolution of mirrors.f.o. report?
resolvectl query mirrors.fedoraproject.org

3

@alciregi Thank you for the reply.

This is what he sent:

mirrors.fedoraproject.org: 2604:1580:fe00:0:dead:beef:cafe:fed1 – link: wlp1s0
2620:52:3:1:dead:beef:cafe:fed7 – link: wlp1s0
2620:52:3:1:dead:beef:cafe:fed6 – link: wlp1s0
2600:2701:4000:5211:dead:beef:fe:fed3 – link: wlp1s0
2605:bc80:3010:600:dead:beef:cafe:fed9 – link: wlp1s0
2600:1f14:fad:5c02:5270:306c:35d6:1f81 – link: wlp1s0
140.211.169.196 – link: wlp1s0
8.43.85.67 – link: wlp1s0
8.43.85.73 – link: wlp1s0
38.145.32.20 – link: wlp1s0
34.211.44.206 – link: wlp1s0
67.219.144.68 – link: wlp1s0
38.145.32.21 – link: wlp1s0
(wildcard.fedoraproject.org)

– Information acquired via protocol DNS in 1.3845s.
– Data is authenticated: no; Data was acquired via local or encrypted transport: no
– Data from: network

Would this indicate DNS is working for him now? A subsequent run of dnf went through successfully and reported ‘nothing to do’.

I just ran it myself, no errors were displayed.