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:19 PM, Sam Varshavchik wrote:
> Steve Dickson writes:
> 
>> 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???
> 
> Inspect what it's your /etc/resolv.conf, confirm that your name server is 127.0.0.10, or something this bizarre.
I guess it is bizarre... 
# 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

> 
> Now look in /run/NetworkManager/no-stub-resolv.conf to see what your real DNS server is. Let's assume that you see it's 8.8.8.8, but you should be able to recognize your usual DNS server in there.
# cat /run/NetworkManager/no-stub-resolv.conf 
cat: /run/NetworkManager/no-stub-resolv.conf: No such file or directory

Who is suppose to create that? It is on /run so it be created on every reboot... 
> 
> Now, perform a test lookup using the dig command, directly, to your real DNS server.
> 
> dig @8.8.8.8 www.yahoo.com
I can't do this because bind-utils was not install and I can not install it
because DNS is broken..

> 
> Make sure you use the IP address you got from no-stub-resolv.conf
> 
> Assuming that this lookup succeeds, proceed as follows:
> 
> systemctl stop systemd-resolved
> systemctl disable systemd-resolved
> rm -f /etc/resolv.conf
> ln -s ../run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf
since there is no no-stub-resolv.conf... 
ln -s ../run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf
# cat /etc/resolv.conf 
cat: /etc/resolv.conf: No such file or directory

> 
> Verify that your DNS service is now working, then announce that you joined the systemd fan club, and ask for your membership information.
I wish I could! :-) 

I think the bottom line is /run/NetworkManager/no-stub-resolv.conf is
is no longer being created... 

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