Temporary failure in name resolution on Ubuntu server 22.04.3 LTS

[Bo Berglund]

On Sun, 26 Nov 2023 05:01:18 -0500, Jeffrey Walton <noloader at gmail.com> wrote:

>On Sun, Nov 26, 2023 at 4:50?AM Bo Berglund <bo.berglund at gmail.com> wrote:
>>
>> I recently performed a do-release-upgrade to move the server from 20.04 to
>> 22.04.3 LTS. This is a non-GUI server system.
>>
>> Now after about a month the DNS system is broken!
>> I get the error in the subject for instance wen doing:
>>
>> $ ping www.sunet.com
>> ping: www.sunet.com: Temporary failure in name resolution
>
>I don't think there's enough information at the moment. I think you
>should show the output of `nslookup --debug` or `dig`.
>
>Additional information that would be helpful is the IP address of your
>site's DNS server, whether IPv4, IPv6 or both are being used, and your
>DHCP configuration options.
>
>> I have googled the problem and the advice I ave found is to edit the
>> /etc/resolv.conf file and add the google DNS server 8.8.8.8
>
>I would avoid Stack Overflow questions and guesses until you determine
>what the problem is.
>
>You will probably get better results with a search like
><https://www.google.com/search?q=troubleshoot+"Temporary+failure+in+name+resolution"+nslookup+dig>.
>

Thanks, I used the advice here:
https://phoenixnap.com/kb/temporary-failure-in-name-resolution

And went ahead and edited the /etc/resolv.conf file and added the two google
servers, then:
sudo systemctl restart systemd-resolved.service

And now the resolution works again!

Why in the world have the Ubuntu maintainers put that comment about NOT editing
teh file there???????

Makes no sense to me.

-- 
Bo Berglund
Developer in Sweden