On Mon, 15 Feb 2021 at 17:39, Steve Dickson <SteveD@xxxxxxxxxx> wrote:
Hello,
I just updated to latest Fedora 33 and
I no longer have any DNS name solution.
The network is up... but...
$ ping www.yahoo.com
ping: www.yahoo.com: Name or service not known
I changed nothing!
How would be the bet way to debug this???
It could be all kinds of things.. I updated this morning and still have DNS so not sure which.
1. what does /etc/resolv.conf say? Mine is pretty default but there are different ways this could be happening:
[ssmoogen@localhost freenode-znc]$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search redhat.com southeast.rr.com
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search redhat.com southeast.rr.com
2. what does systemd-resolv say
[ssmoogen@localhost freenode-znc]$ systemd-resolve www.yahoo.com
www.yahoo.com: 74.6.143.25 -- link: ens1u2u1u2
74.6.143.26 -- link: ens1u2u1u2
2001:4998:124:1507::f001 -- link: ens1u2u1u2
2001:4998:124:1507::f000 -- link: ens1u2u1u2
(new-fp-shed.wg1.b.yahoo.com)
-- Information acquired via protocol DNS in 1.5ms.
-- Data is authenticated: no
www.yahoo.com: 74.6.143.25 -- link: ens1u2u1u2
74.6.143.26 -- link: ens1u2u1u2
2001:4998:124:1507::f001 -- link: ens1u2u1u2
2001:4998:124:1507::f000 -- link: ens1u2u1u2
(new-fp-shed.wg1.b.yahoo.com)
-- Information acquired via protocol DNS in 1.5ms.
-- Data is authenticated: no
3. again if you are set up with systemd-resolv does it show up as broken in systemctl or
[root@localhost ~]# ss -npl| grep systemd-resolv
u_dgr UNCONN 0 0 * 39594 * 16930 users:(("systemd-resolve",pid=7472,fd=3))
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=16))
udp UNCONN 0 0 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=11))
udp UNCONN 0 0 [::]:5355 [::]:* users:(("systemd-resolve",pid=7472,fd=13))
tcp LISTEN 0 4096 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=12))
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=17))
tcp LISTEN 0 4096 [::]:5355 [::]:* users:(("systemd-resolve",pid=7472,fd=14))
u_dgr UNCONN 0 0 * 39594 * 16930 users:(("systemd-resolve",pid=7472,fd=3))
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=16))
udp UNCONN 0 0 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=11))
udp UNCONN 0 0 [::]:5355 [::]:* users:(("systemd-resolve",pid=7472,fd=13))
tcp LISTEN 0 4096 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=12))
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=7472,fd=17))
tcp LISTEN 0 4096 [::]:5355 [::]:* users:(("systemd-resolve",pid=7472,fd=14))
Stephen J Smoogen.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure