• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Question DNS for subdomains not working on a private domain

jjohnsonmvdexpress

New Pleskian
I have taken over a Plesk setup that the previous administrator is not available to offer support. I am also new to Plesk.

We have VPN based internal private network, so the domains in question are only accessible from the Plesk server over the VPN.

I have a domain that is working, for example: ecommerce.ad.mydomain.com

I setup a subdomain from there, dev.ecommerce.ad.mydomain.com.

I setup my windows 11 computer with the internal and external dns (i.e. DNS: 10.10.10.51, 75.75.75.75) so that nslookup uses the internal dns first.

When I nslookup on the subdomain I get the internal IP that it is on.

When I ping (in Powershell), curl (in Powershell), or open the URL in a browser, I get "could not find host" and "The remote name could not be resolved" types of errors.

When I modify my windows hosts file to have the IP and name of the subdomain (i.e. 10.10.10.52 dev.ecommerce.ad.mydomain.com), then ping, curl, and my browser are able to access to the webpage.

I am not sure what step I am missing here.
 
Back
Top