Temporary failure in name resolution

[bostic]

Hi, team!

Yesterday and today I get letters to mail:

sudo /usr/local/hestia/bin/v-update-sys-queue restart
sudo: unable to resolve host mydomain.com: Temporary failure in name resolution.

sudo /usr/local/hestia/bin/v-update-sys-rrd
sudo: unable to resolve host mydomain.com: Temporary failure in name resolution

sudo /usr/local/hestia/bin/v-update-sys-queue backup
sudo: unable to resolve host mydomain.com: Temporary failure in name resolution

sudo /usr/local/hestia/bin/v-update-sys-hestia-all
W: Failed to fetch https://apt.hestiacp.com/dists/buster/InRelease Temporary failure resolving ‘apt.hestiacp.com’
W: Some index files failed to download. They have been ignored, or old ones used instead.
W: Failed to fetch https://apt.hestiacp.com/dists/buster/InRelease Temporary failure resolving ‘apt.hestiacp.com’
W: Some index files failed to download. They have been ignored, or old ones used instead.

Debian 10.11 Hestia:v1.5.11 Auto update.

What went wrong?
This is due to automatic update?

[Raphael]

DNS stopped working on your server, check your dns configuration. The server also may be slow, due to missing lookups.

[bostic]

Hey,ScIT
Thanks for the answer, I will check the configuration.

[AlexMKTD]

I consult where this DNS configuration is reviewed, since I have the same problem, if you could provide more details I would greatly appreciate it.

[eris]

/etc/resolv.conf

Check if ping google.com works or otherwise check your network configuration

[bostic]

Hi! Today I received mistakes again
Check if ping google.com works - WORKS
/etc/resolv.conf - There is no file
Found a file - etc/resoivconf/run/resolv.conf:
nameserver (ip-contabo.com ,my vps )
nameserver (ip-contabo.com ,my vps )
search invalid

I need to create a file separately in /etc/ ?

[AlexMKTD]

Those are the emails that I am receiving, I have already pinged google from my server and it is responding as seen in the screenshot

I appreciate more instructions to solve this problem.

[eris]

@AlexMKTD what happens when you run on your server:

nslookup vps.alexhurtadomktd.com

You can also add
127.0.0.1 hostname

to your /etc/hosts file

[eris]

If ping google.com is working it should be fine what happens when you run:

nslookup hostname.com

[AlexMKTD]

This is the response I get on my server.

[bostic]

@eris

hostname.com

Server:         213.136.95.10
Address:        213.136.95.10#53

Non-authoritative answer:
Name:   hostname.com
Address: 144.91.73.12

[bostic]

Maybe a problem on the side contabo ?