• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Internal DNS Question

gesora

New Pleskian
Server operating system version
Windows Server 2019
Plesk version and microupdate number
Plesk Obsidian
I'm building a new infrastructure for a customer and he has an internal DNS binds for their infrastructure, actually all the developers need that the Plesks servers can't resolve their internal GITLAB Repos and some DB Galera Clusters servers the subnets have the corrects ACL to reach them, but I don't know what will be the correct way to accomplish this, should I simply create a pointer using hosts or instead create a pointer for their zones and have the Plesks server to use their DNS servers for it.
 
Back
Top