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

Plesk 12.5 DNS Server Stopped Responding Overnight

Olly

New Pleskian
I've come into work this morning to find all our websites are down because Plesk isn't responding to DNS requests externally.

I've tried restarting the DNS service, and reinstalling it. Running a portscan to our IP shows that the DNS port is open.

If you SSH into the server and run "nslookup whitesweb.co.uk 127.0.0.1" it returns the correct response, any ideas what might be causing this?
 
I'm sure, "Domain name server" has a tick against it, and this morning I opened "System policy for incoming traffic" to rule out the firewall.
 
So, can you connect to this server outside with

telnet servername.com 53

?
 
Well. This means that DNS port 53 is not accessible on your Plesk server. I suggest you check your network infrastructure, firewalls, routers, etc.
 
Back
Top