• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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