Proxmox cannot resolve local hosts

[HTP.ProXy]

Hello,

I just finished my first Proxmox installation, the web interface was available after a few minutes, but now I am struggling.
It's not possible to resolve local hostnames, but it is woking fine with domains.

Is there something I am missing?

Thank you!

 

[dherzig]

Hi HTP.ProXy,

could you please elaborate on what you are trying to achieve?

Do I understand correctly, that you can:

ping $KNOWN_IP_OF_HOST

But not:

ping $LOCAL_MACHINE_NAME_OF_SAME_HOST

What kind of machines are you trying to access using local hostnames and from where (PVE-Host, Guest-VM)?

Can you confirm you can access these machines from other devices in your network by local hostnames?

Are all machines in your network using the same networking hardware?

Best regards,
Daniel

 

[HTP.ProXy]

Hello Daniel,

I am trying to ping my Synology NAS (hostname ds920) from the PVE-Host.

ping ds920

returns

ds920: Name or service not known

But pinging the IP of the NAS works without any issues and also pinging google.com works.

I guess there is any service missing rhat would resolve local hostnames?

Thank you
Stefan

Edit: It is the same result when trying to ping the hostname from a Guest-VM!

 

[UdoB]

I guess there is any service missing rhat would resolve local hostnames?

Either you setup the "real" solution - being a DNS server, possibly redundant.

Or you just edit /etc/hosts... - man hosts tells you more, including showing some examples.

 

[HTP.ProXy]

Why is nearly every device in my local network able to resolve local hostnames but not Proxmox?

Every NAS, every rpi, even every Nividia Shield is able to resolve them.

 

[dherzig]

Hi Stefan,

Are all devices connected to the same networking hardware? Are there any firewall rules in place (on the PVE-host, on the router)?

Could you try running the following to check if you get an answer to a dns reverse query, and share the output:

dig -x $IP_OF_ds920

Best,
Daniel

 

[HTP.ProXy]

Hello Daniel,

thank you for the answer. All devices are connected to the same networking hardware and there are no firewall rules.

This is the result of 'dig':

dig -x 192.168.1.12

; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> -x 192.168.1.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42546
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;12.1.168.192.in-addr.arpa.     IN      PTR

;; AUTHORITY SECTION:
168.192.in-addr.arpa.   10800   IN      SOA     localhost. nobody.invalid. 1 3600 1200 604800 10800

;; Query time: 16 msec
;; SERVER: 10.64.0.1#53(10.64.0.1) (UDP)
;; WHEN: Tue Feb 25 13:10:14 CET 2025
;; MSG SIZE  rcvd: 113

Best regards,
Stefan

 

[dherzig]

Hi Stefan,

thanks for sharing.

So you have a custom DNS-Server at 10.64.0.1? Is it properly configured to forward local hostnames? Are all your devices in your network configured to use that one? Could you run the same command from one of your eg. pis to double-check if the settings are the same?

Best regards,
Daniel

 

[HTP.ProXy]

Hi Daniel,

sorry the above result was not correct. I ran it one a Guest VM that is connected to a VPN.

This is the result of dig on the vpe itself:

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42721
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;12.1.168.192.in-addr.arpa.     IN      PTR

;; AUTHORITY SECTION:
168.192.in-addr.arpa.   37      IN      SOA     localhost. root. 1 604800 86400 2419200 604800

;; Query time: 3 msec
;; SERVER: 192.168.1.16#53(192.168.1.16) (UDP)
;; WHEN: Tue Feb 25 13:36:56 CET 2025
;; MSG SIZE  rcvd: 103