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

named service problem (New Installation)

KamalG

Basic Pleskian
service named restart
Stopping named: [ OK ]
Starting named:
Error in named configuration:
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
zone domainname/IN: has no NS records
zone domainname/IN: not loaded due to errors.
_default/domainname/IN: bad zone
zone 161.91.118.in-addr.arpa/IN: loaded serial 1348979213
[FAILED]

How can I fix this problem, please help it's a fresh installation. already have the dns configured.
 
Thanks this is fixed.

Would be nice to offer the solution rather than just stated "Thanks this is fixed".. This is a forum where we should all help each other..

I solved the issue by fixing missing DNS A or AAAA records for the main Nameserver for your domains. For example:

ns1.yourdomain.com A record YOUR IP Address
ns2.yourdomain.com A record YOUR IP Address

Optional for your master domain - Should be done if you use your Plesk DNS as a main DNS server. This wouldn't apply to me since i use Cloudf(lare) as a DNS provider

yourdomain.com NS record ns1.yourdomain.com
yourdomain.com NS record ns2.yourdomain.com

Apply and save the settings. If you are receiving the error for many domains. Be sure to add the top configuration a records to the main DNS template, then apply to all domains.

Once this is completed, the Bind DNS server errors should be gone. :)
 
Back
Top