[SOLVED] Can't reach CT's using hostname

mspielberger

Renowned Member
Mar 4, 2013
14
1
63
Hi

I've installed Proxmox on top of Debian 9, then upgraded everything to Buster & Proxmox 6 (in hope, it might solve my problem), but unfortunately it did not help.

Host and VMs have internet access and everything is fine.
I can access the VMs using their IPs, but not using their Hostname and I am at a loss to find out whats not working.

Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug enp2s0

auto enp2s0
iface enp2s0 inet manual

auto vmbr0
iface vmbr0 inet static
    address  172.16.16.56
    netmask  24
    gateway  172.16.16.1
    bridge-ports enp2s0
    bridge-stp off
    bridge-fd 0

Firewall is disabled, on all instances

I hope I have added / attached all the correct information?


Thanks!
 

Attachments

  • px.png
    px.png
    133 KB · Views: 10
  • px2.png
    px2.png
    64.7 KB · Views: 10
Last edited:
the node is using 172.16.16.1 - so thats the ip of the router
vms use host's settings

I can reach the Host using the hostname, just not the vms?
Ping / Traceroute work (which is expected)
 
the node is using 172.16.16.1 - so thats the ip of the router
vms use host's settings

I can reach the Host using the hostname, just not the vms?
Ping / Traceroute work (which is expected)

and you have DNS records for your VM on your DNS server on 172.16.16.1?
 
yes ;)

Code:
ping test.xx.yy
PING test.xx.yy (176.16.16.203): 56 data bytes
64 bytes from 176.16.16.203: icmp_seq=0 ttl=46 time=194.184 ms
64 bytes from 176.16.16.203: icmp_seq=1 ttl=46 time=160.701 ms
 
you show here that you can ping a hostname "test.xx.yy".?

so it looks it works.
 
No :/

I have the host running at px.xx.yy, and I can access the GUI at https://px.xx.yy:8006
The DNS is entered into the Firewall an all is good.

First VM is test.xx.yy, DNS is entered, and ping works.
AFAIK the ping will ask the router (= DNS) for the IP of the FQDN and then will send the ping. As I've said, ping works.

So I can access http://176.16.16.203 but not test.xx.yy
When I access test.xx.yy I get a ERR_CONNECTION_REFUSED
 
Ok, proxmox is not at fault, it is my DNS / Firewall.
Thanks for your quick help tom!

(by adding the server manually in /etc/hosts/ I could reach them, ruling out proxmox as the problem)
 

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!