Re: Don't update to the latest f33!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 2/15/21 6:00 PM, Stephen John Smoogen wrote:
> 
> 
> On Mon, 15 Feb 2021 at 17:39, Steve Dickson <SteveD@xxxxxxxxxx <mailto: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 <http://www.yahoo.com>
>     ping: www.yahoo.com <http://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:
> # 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 <http://redhat.com> southeast.rr.com <http://southeast.rr.com>
This is on a server in the cloud.. which might the problem but it
was not before the update. Here is what the /etc/resolv.conf

# 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

> 
>  2. what does systemd-resolv say
> [ssmoogen@localhost freenode-znc]$ systemd-resolve www.yahoo.com <http://www.yahoo.com>
systemd-resolve www.yahoo.com
www.yahoo.com: resolve call failed: No appropriate name servers or networks for name found

I do find this odd... a second network interface. Not sure
where that came from... 

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.108.0.2  netmask 255.255.240.0  broadcast 10.108.15.255
        inet6 fe80::a491:39ff:feb6:3c7e  prefixlen 64  scopeid 0x20<link>
        ether a6:91:39:b6:3c:7e  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 19  bytes 1370 (1.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Obviously that is a non route-able address... I did turn i off but
it did not help with the DNS.. 

> 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
It seems to be live... https://paste.centos.org/view/52f7ce26

Thanks!

steved.
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux