• 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.

Bind Name Servers

L

Linux98

Guest
Hi,

me = Novice User


I am trying to get Plesk to recognize (bind?) my nameserver to my web site domain.

However, I am not sure how to make Plesk 1) recognize ns1.mynameserver.net, and 2) connect www.mydomain.com to ns1.mynameserver.net.

Current set up under Clients >Domains > DNS Zone:
<PTR> My Dedicated IP Address/ 24 = mydomain.com
<A> My Dedicated IP Address
<NS> ns1.mynameserver.net
<NS> ns2.mynameserver.net
Everything else is default.

Current set up under Server Asministration > IP Address Management:
<MyIPAddress> 255.255.255.255 Clients=1 Hosting=1

Current set up under Server Adminsitration > DNS Zone Template:
<NS> ns1.mynameserver.net
<NS> ns2.mynameserver.net


When I try to access the public web site from my browser I get "This web site cannot be found". I belive the domain settings are accurate at the registrar for both mydomain.com and ns1.mynameserver.net. They even ping through DNSSTUFF.COM.

Did I miss something to bind my nameserver to my Plesk server?

Thanks
 
I tried both.

The CNAME is set up to accept www.___.com and just ____.com. I am able to ping them, get a trace route, and see the A and NS records for the domain. In addition, the nameservers display the proper IP address on a DNS lookup. So my guess is that my problem exists at my web server.

Ultimately, I think I just need to figure out how to 1) bind my nameserver to my dedicated IP address and 2) bind my nameserver to my public web site address.

I'll just engage in a game of "guess and check" until I figure this out. Thanks
 
Back
Top