Question Subdomain needs own dedicted WAN IP

[LTR75-001]

Server operating system version

Ubuntu 22.04.3 LTS

Plesk version and microupdate number

Plesk Obsidian Version 18.0.57

Hello,

Currently under Plesk, we are hosting a domain www.domain.com, along with an added subdomain admin.domain.com. Both domains fall under the same subscription. The site is still under construction, so the DNS references on the internet still point to a different IP, other than the IP of our Plesk server.

Because both domains are under the same subscription, only one dedicated IP can be assigned (as it seems). This IP number applies to both domains, and apparently, it is not possible to assign a different dedicated IP to the primary domain than to the subdomain.

The web designer has redirected domain.com and admin.domain in the host file on his Windows computer to the new IP of the Plesk server. Now the problem is that when the domains are opened within the web browser on the web designer's computer, both domains lead to the admin.domain.com (portal) page, even when viewing the primary domain. For us, this is a puzzle that we want to solve by providing the subdomain with a different dedicated (WAN) IP number.

Is it possible to assign a different dedicated IP number to the subdomain (admin.domain.com) than to the primary domain? This way, the host file can point to two different IPs.

 

[Dave W]

It should be possible to use the same IP for domain.com and admin.domain.com in your hosts file and access the different sites.

Sounds like theres some other issue going on.

 

[WebHostingAce]

Dave is right. Sounds like there is some other issue going on.

FYI, it is possible to add the subdomain as a separate subscription then assign a dedicated IP, separate system user etc..

 

[LTR75-001]

Possible additional information. As soon as we disable the subdomain so that only the primary domain is still active, we end up on the default Plesk web page when we open the primary site. Could it be something in Apache?

 

[mow]

Could it be something in Apache?

You'd have to check /etc/apache2/plesk.conf.d/ (and probably /etc/nginx/plesk.conf.d/) for that. Also, you might have a .htaccess lying around somewhere.