Server Aliases have wrong IP

The server aliases say that they will be using the real external address, but it's different than the parent server. If I create a new alias it has the correct IP. These aliases have been active for almost a year, but I think things got borked when I upgraded from VMin 3.49 to 3.69. Is there a way to have the aliases check thier IP against the parent and change if necessary?



So did you change the IP of a parent domain, but it's aliases IPs did not get updated?

I have not changed the IP's. The main server IP ends in 242 and the reseller range starts at 250, however all server aliases now have 250. All of the sub servers are ok. It's really strange and I only noticed after the update to VMin

That's odd, an upgrade shouldn't change any IP addresses.

If you create a new alias domain for a virtual server that is on the .242 address, does it also get the .242 address?

Yes, if I create a new alias it uses the correct IP of .242

I agree that the upgrade shouldn't change the IP, but I can't think of anything else that has happened recently. Luckily the customer hasn't noticed so there is some time to track it down. I could delete the aliases and recreate them but I was hoping there might be some sort of tool similar to the Re-Check Module that would compare and change to match if needed.

Perhaps they were created on the wrong IP initially?

It is possible to have aliases on different IPs, and actually useful in some cases. For example, a system might have external and internal network interfaces, and host the same website with different domain names for external and internal users..

Sorry for the delay in responding, I was out of town. So I should either delete and recreate so that the real IP on the alias is correct or switch the alias from using the real IP of the parent to the IP that matches the parent?

Yes, either would work..

Is there a fast way to change all aliases for the same parent?

You could do it using the command-line API, with with virtualmin modify-domain --domain --ip x.x.x.x command, run once for each domain.

You may find the need to check the status of your domains DNS records, or check the Name Servers to see which records the servers are pulling. Launch Windows Command Prompt by navigating to Start > Command Prompt or via Run > CMD. Type NSLOOKUP and hit Enter.