I've had dns problems when multiple programs were fighting over
/etc/resolv.conf, thinking leases had timed out when they hadn't
and other annoying conflicts. Might want to monitor the resolv.conf
file and see if it is changing out from under you when it goes from
working to not working.
On Sun, Nov 27, 2022 at 1:10 PM Paolo Galtieri wrote:
>
> I was a little premature in saying thins started working. It seems to
> be very hit and miss. Wireshark shows many dns requests as refused, but
> then they start to work for a while and then start failing again.
>
> If I run dig cnn.com
I was a little premature in saying thins started working. It seems to
be very hit and miss. Wireshark shows many dns requests as refused, but
then they start to work for a while and then start failing again.
If I run dig cnn.com from my secondary dns server I get:
; <<>> DiG 9.16.33-RH
The reason there are old repos is because I've been following the
dnf-system-upgrade docs for a long time. Strangely after I posted the
message it all started working. I have no idea why it took so long
before things started to work.
Paolo
On 11/27/22 07:55, Jeffrey Walton wrote:
On Sun,
On Sun, Nov 27, 2022 at 10:45 AM Paolo Galtieri wrote:
>
> I just upgraded from fedora 36 to 37. There were no errors reported but
> after the update I get:
>
> dnf list all
> Adobe Systems Incorporated 0.0 B/s | 0 B 00:00
> Errors during downloading metadata for repository
I just upgraded from fedora 36 to 37. There were no errors reported but
after the update I get:
dnf list all
Adobe Systems Incorporated 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'adobe-linux-x86_64':
- Curl error (6): Couldn't resolve host name for
