• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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