• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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