Joe Zeff: > [joe@khorlia ~]$ cat /etc/resolv.conf > # Generated by NetworkManager > search zeff.us > nameserver 8.8.8.8 > nameserver 8.8.4.4 Looks normal. I'd expect the google DNS servers to be working well. > [joe@khorlia ~]$ cat /etc/nsswitch.conf > # > # /etc/nsswitch.conf > # > # An example Name Service Switch config file. This file should be > # sorted with the most-used services at the beginning. > # > # The entry '[NOTFOUND=return]' means that the search for an > # entry should stop if the search in the previous entry turned > # up nothing. Note that if the search failed due to some other reason > # (like no NIS server responding) then the search continues with the > # next entry. > > #hosts: db files nisplus nis dns > hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname > It seems to me that having an abort function in the middle of the list of things to check, rather than at the end, might be a cause of grief. I've never understood why some are configured that way. You could try modifying that line. On my ye olde CentOS 7 and Fedora 36, mine just has hosts: files dns (I don't make use of mdns/zeroconf/automangle) The "files" option means to check the /etc/hosts file, which is typically just used for the localhost addresses, now. [tim@rocky ~]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 > [joe@khorlia ~]$ dig slashdot.org > > .... > > ;; ANSWER SECTION: > slashdot.org. 300 IN A 104.18.28.86 > slashdot.org. 300 IN A 104.18.29.86 Same as me, so DNS queries are being answered correctly, by the Google DNS servers: > ;; Query time: 109 msec > ;; SERVER: 8.8.8.8#53(8.8.8.8) You could see if doing "dig slashdot.org @8.8.8.8" gets the same results as "dig slashdot.org @8.8.4.4" (they do, here). It is resolving. It looks like you're having a web browser issue (not connecting, or something jamming in the cache). I'm guessing you've restarted your browsing during this situation. But have you tried flushing its cache, too? You can flush the cache without destroying saved logins, history, etc. Do you use one of those HTTPS-only plug-ins? Do you get different results for attempting http://slashdot.org/ versus https://slashdot.org ? Do you have more than one browser installed on the problem machine? Can you try installing another one, even if just temporarily? -- uname -rsvp Linux 3.10.0-1160.80.1.el7.x86_64 #1 SMP Tue Nov 8 15:48:59 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. _______________________________________________ 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
