• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Resolved Nameserver is on Server 1 but hosting clients on Server 2 don't resolve

FutureX

Basic Pleskian
Server operating system version
AlmaLinux 8.6
Plesk version and microupdate number
18.0.42 Update #1
I have 2 servers S1 and S2, I setup a nameserver on S1 myserver1.com and added glue records on Google Domains so I have ns1.myserver1.com and ns2.myserver1.com. There are 2 domains on S1 which resolve fine when I set the custom name servers on Google domains to ns1.myserver1.com and ns2.myserver1.com. My problem is I can't get any domains on S2 to resolve at all. I've done the same setup on Google Domains for every domain on S2, set the custom name servers to ns1.myserver1.com and ns2.myserver1.com. In the DNS setup of each domain on S2 the NS record is set to the same ns1.myserver1.com and ns2.myserver1.com but nothing is resolving on S2.

I know I just missing a key concept here but can't see it.
FutureX
 
I found my answer. I'm using Digital Ocean to handle the DNS. You can setup vanity nameservers so it's your host hame instead of theirs and there is an extension for Plesk to sync the DNS on Plesk with Digital Ocean. It works great and the sync is instant and it's free on DigitalOcean!
 
Back
Top