• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Solved: DNS Server Crashed, failed to start

Status
Not open for further replies.

Xavier12

Regular Pleskian
Hey guys,

It seems the servers dns will not resolve and has crashed. When starting the "Named" service, here is the error:

Error in named configuration:
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
zone 215.170.107.in-addr.arpa/IN: loaded serial 1433121512
zone lanewgirl.com/IN: NS 'ns.mydomain.com' has no address records (A or AAAA)

zone mydomain.com/IN: not loaded due to errors.

_default/mydomain.com/IN: bad zone

zone mydomain2.com/IN: NS 'ns.mydomain2.com' has no address records (A or AAAA)

zone mydomain2.com/IN: not loaded due to errors.

_default/mydomain2.com/IN: bad zone

Please advise, thanks
 
The solution would be to use a valid dns-template or at least add an a-record to that zone.
Are you using plesk as primary dns for that domain?
 
Hi Oliver,

Thanks for the response. Yes. Zones were set up. The issue was that we tried to duplicate a site and the vps crashed because of no disk space. We deleted files to get the vps back in working order. Since then, the DNS issue occurred.

When starting DNS in plesk, here is the error

Error: Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start
('--start', 'dns')

Please advise, thanks
 
RESOLVED

Seem to have fixed it by going to the default template dns settings in Tools & Settings / DNS Template, then resetting to default. From there, re-add nameserver A Records, etc.
 
Status
Not open for further replies.
Back
Top