Subdomains of a private IP address fail

I created a subdomain of my main site in the usual way (in the /domains folder). It's therefore accessible by the main site administrators, which is what I want in this case. Everything worked OK.

Then in order to get SSL working for secure logins I purchased a dedicated IP for the main site and assigned it to that site as a "private" IP address. (The process for IPv4 and IPv6 is different, which is confusing but I worked it out). I installed a certificate and changed my nameserver settings and https connections then worked fine. (By the way, I was pleasantly surprised to find the unencrypted site continued to work fine at the original IP address while the DNS changes propagated, no downtime.)

The problem was, the subdomain was now broken - it was serving pages from the parent domain instead of the subdomain. The IP address of the subdomain hadn't changed and Virtualmin wouldn't let me change it to the private IP because it was "already in use".

The solution was to change the new dedicated IP to a secondary "shared" IP address and assign that to both the main domain and the subdomain.

I suggest the solution is to prevent subdomains of a private IP address being created in the first place (perhaps by automatically changing the IP address to a secondary shared one) since they're doomed to fail in a non-obvious way.



How did you create this domain? Was it just using the "Create sub-server" link, or was it using the less common sub-domain feature in Virtualmin (in which the web content for the subdomain is served from a sub-directory under public_html) ?

philmck's picture
Submitted by philmck on Sat, 08/15/2015 - 18:01

It was created using Virtualmin > Create Virtual Server > Sub-server.

(I didn't even know the sub-domain feature existed, I discover it's disabled by default and now know more about it than I should!)