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

Is this an issue?

Peter-

Basic Pleskian
Hello,

I started using opennms since I got a couple emails saying my server was "not there" for some requests.

After 12 hours, my stats look like this:

http://screencast.com/t/6rEgkLP5W

DNS is answering but, apparently it's not a proper answer (so they say).

The error message looks like this: DNS outage identified on interface xxx.xxx.xxx.xxx with reason code: Received an invalid DNS response for address: xxx.xxx.xxx.xxx.

Where should I look? My DNS is entirely configured using Plesk from the web interface. No alteration in the files or anything.

On a thread on their forum, someone suggested I should remove this line from the config:

<parameter key="fatal-response-codes" value="2,3,5" /><!-- ServFail, NXDomain, Refused -->

Altering the tests params doesn't seem a good solution for me, unless their tests suck.

Thanks
 
Back
Top