[SOLVED] VMs not accessible from internal network using fqdn

[adi.prabhakar]

Hello,

I am new to this community and virtualisation in general.

I have the following setup:
- Proxmox 6.2-4 running on a dedicated server dell R720
- Multiple static ips 82.68.xx.x1 - 82.68.xx.x6
- virtual machine 1 - running virtualmin to host websites with IP address 192.168.1.133
- virtual machine 2 - running webmin as a slave dns for VM1 with ip address 192.168.1.150
- virtual machine 3 - running exchange server with ip address -1 192.168.1.24
- Draytek vigour 2860 router

The router helps me to direct the traffic from the internet to the relevant vm. For example, the external ip for vm 1 is 82.68.xx.x1 and all the relevant ports which this vm requires are open in the router configuration. Same goes for the other VMs

I have the following setup in Proxmox networking:
- four active network devices eno1 to eno4
- Linux Bridge vmbr0 with ipv4/cidr 192.168.1.100/24, gateway 192.168.1.1 and bridge port as eno1. I use this bridge to access proxmox on the local network
- Linux bond bond 0 with posts/slaves as eno2 eno3 eno4 in balance-albn mode
- Linux Bridge vmbr 1 with bridge port as bind0 - This bridge is allocated to all the VMs for internet access

Problem
If I want to access the websites, emails, VMs from an external network, everything works fine using just the fqdn which are pointed in the dns to static ip addresses. However, if I am connected to the same IP subnet of 192.168.1.x, the fqdn does not work and I have to type local ip addresses of each vm to gain access.

What am I doing wrong here please?

 

[Stefan_R]

It seems like you're trying to access your VMs via their external public IPs from within your network. This requires your router to support hairpinning (a feature of NAT), check if it does and enable it.

Alternatively, you can use split-DNS, so your internal hosts get the internal IP address when asking your local DNS server.

 

[adi.prabhakar]

It seems like you're trying to access your VMs via their external public IPs from within your network. This requires your router to support hairpinning (a feature of NAT), check if it does and enable it.

Alternatively, you can use split-DNS, so your internal hosts get the internal IP address when asking your local DNS server.

Thanks Stefan_R. Researching about hairpinning resolved my issue. My router does not support this but I was able to use a feature called LAN DNS in the router. Now, if the request for fqdn is originating from the internal network they get routed to the internal IP address