can not ping to DNS Server but other IPs are OK

Homer-S

Member
Nov 18, 2020
31
2
13
52
Hello,
I am running 7.4-17.
I recognized that there is some issue because apt update were not able to receive new packages.
I tried from my PVE host:
ping -c 4 192.168.100.1 #(my fritz box)
or ping -c 4 google.com

both results in all lost

if I try an other internal IP 192.168.100.22 it is working

If I am pining from inside an VM everything is working like expected.

Where should I look for to fix this?

Thanks
 
Please post your network configuration and the configured DNS servers.
 
I hope I am posing the right ones:
1704960645883.png
The second DNS entry here had been added recently for testing reason after the issue occured. on IP 2 there is an addguard home server. But it did not solve it
1704960675018.png
 
Delete the search domain and then see if the name resolution works. Apparently you also have a problem with your gateway, so please also ip r.
 
I deleted it. Is there a reboot necessary?
Code:
ping -c 4 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.

--- 192.168.100.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3053ms

is this what you needed?

Code:
ip r
default via 192.168.100.1 dev vmbr0 proto kernel onlink
192.168.100.0/24 dev vmbr0 proto kernel scope link src 192.168.100.10
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!