On 12/17/22 17:48, Sam Varshavchik wrote:
ToddAndMargo via users writes:
All this silliness started as of Fedora Core 37.
There were no issues with 36.
How certain are you that you had systemd-resolved installed in 36, and
it didn't get pulled in during the upgrade to 37?
This particular rpm package has a tendency to get pulled in as a weak
update dependency, every once in a while. It
# host gbis.com
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; no servers could be reached
And two minutes later:
# host gbis.com
gbis.com has address 54.151.57.48
gbis.com mail is handled by 0 gbis.com.
But it does not hold. Back and forth and
back and forth
Yes. I've seen this. Despite bind-chroot running on the same
blankety-blank server, if I allowed systemd-resolved to handle DNS
queries on this server it will occasionally try to convince me that the
DNS server is unreachable.
The only way to fix this reliably is to uninstall systemd-resolved.
I did. It helped a little.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
