|OS type and version
||Ubuntu Linux 20.04.5
||All installed packages are up to date
I do have a server at Hetzner-Cloud where I’ve playing a bit around to test some stuff.
The Server does have the IP: 220.127.116.11 AND a Failover-IP/Floating-IP: 18.104.22.168
I’ve configured virtualmin like that:
Virtualmin > Addresses & Networking > Shared IP:
But it put me all the time the IP of “49…12.235.22” into DNS-Settings.
I’ve found a setting in Virtualmin-Config to force another IP:
But this produce following
Notice / Warning if I do check the config:
Question: Is there better way to pre-configure that the right IP (Floating-IP) is used in DNS-Settings if I create a new VirtualServer, or can I ignore the warning and go with it like I’ve set it up now?
Are you using Ubuntu 22.04 ?
Is the vps/server using netplan for network management
Ok I had a similar issue using netplan see here https://forum.virtualmin.com/t/ubuntu-22-04-switching-network-configuration-from-dhcp-to-static/116930/35 I resolved this by reverting to ubuntu 20.04 and disabling netplan … not sure but there maybe an problem with netplan
I have a feeling your “floating” address is meant for “inbound” not “outbound” connections and is not actually directly assigned to your server. That’s likely while your server IP address is being detected as the one ending in “.22”.
Did configured the IP like described by the Provider: https://docs.hetzner.com/cloud/floating-ips/persistent-configuration#ubuntu-2004
Don’t now what steps may be needed to make it also used as outbound ip.
Does your network adapter actually utilize “eth0” or another naming schema? For instance my laptop which runs Ubuntu uses the naming schema of “enp4s0”… and/or are both IPs using the same adapter name as this WILL NOT work either generally speaking… Assuming you are using the documented naming schema of “eth0” then a second IP would need to be called “eth0:1” or similar which makes it a “virtual network adapter” allowing both IPs to use the same physical network adapter in the system.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.