Temporary failure in name resolution Proxmox v7.4-3

detachable

New Member
Jan 4, 2023
13
4
3
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.

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.