[SOLVED] Temporary failure in name resolution

[detachable]

Whenever I try to perform basic network tasks like pinging a website (e.g., ping example.com) or updating packages with apt update, I get the error message: "Temporary failure in name resolution." This issue has been persisting for some time now, and it's causing problems with my system updates and internet connectivity. v 7.4-3
1. ping proxmox.com
Output:
Temporary failure in name resolution
2. ping 1.1.1.1
Output :
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=46.6 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=46.5 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=46.5 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=52 time=46.6 ms

3. sudo apt update
Output
W: Failed to fetch http://ftp.debian.org/debian/dists/bullseye/InRelease Temporary failure resolving 'ftp.debian.org'
W: Failed to fetch http://ftp.debian.org/debian/dists/bullseye-updates/InRelease Temporary failure resolving 'ftp.debian.org'
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease Temporary failure resolving 'security.debian.org'
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease Temporary failure resolving 'download.proxmox.com'

4. Getting this from proxmox dashbaord
Can't connect to packages.debian.org:80 (Temporary failure in name resolution) (500)

cat /etc/resolv.conf
Output:
search local
nameserver 192.168.1.1

resolvectl
Output:
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

 

[Chris]

Hi,

search local
nameserver 192.168.1.1

is this your nameserver? if not you will have to setup the correct one in here. Check if you can ping the nameserver and test with nslookup proxmox.com.

resolvectl

Proxmox VE does not use systemd-resolved so remove that if it is installed on your system, as it might interfere with DNS resolution.

 

[detachable]

Hi,

is this your nameserver? if not you will have to setup the correct one in here. Check if you can ping the nameserver and test with nslookup proxmox.com.


Proxmox VE does not use systemd-resolved so remove that if it is installed on your system, as it might interfere with DNS resolution.

Hi Chris,
I'm able to ping nameserver (192.168.1.1).

nslookup proxmox.com
Output:
;; connection timed out; no servers could be reached

systemctl status systemd-resolved
Output:

systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; ve>
Active: inactive (dead)
Docs: man:systemd-resolved.service(8)
man: org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network->
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>

Additional
This issue is in only host machine VMs & LXCs working fine.

 

[Chris]

Output:
;; connection timed out; no servers could be reached

Either 192.168.1.1 is not running DNS or something is blocking your traffic. You might want to use the name server configured in the VMs/CTs if that is working.

systemctl status systemd-resolved
Output:

systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; ve>
Active: inactive (dead)
Docs: man:systemd-resolved.service(8)
man: org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network->
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>

As stated, Proxmox VE is not using systemd-resolved, so it is recommended to uninstall related packages from your system, as they might interfere.

 

[detachable]

Either 192.168.1.1 is not running DNS or something is blocking your traffic. You might want to use the name server configured in the VMs/CTs if that is working.


As stated, Proxmox VE is not using systemd-resolved, so it is recommended to uninstall related packages from your system, as they might interfere.

I updated /etc/resolv.conf with

search .
nameserver 1.1.1.1

& it's working. Thanks

 

[jaredholloway94]

I had to give my node an address in the subnet where the default gateway was.
That address did not have to be assigned to the same interface where the default gateway was set.

 

[CrawfordHulk]

Another Fix is Proxmox DNS only uses FQDN so this was the fix for Veeam worker issue for me

 

[Ditya]

Another fix, if DNS is configured correctly, then it is worth checking whether your router has added your hypervisor to the blacklist by MAC address, I double-checked everything and it turned out that was the problem. I hope that this will be useful to someone.

 

[Number0ne]

In my case I forgot the firewall was on and was blocking port 43 and 53 so I had to allow those before my nameserver worked