BIND misconfiguration can trigger DNSPROBE FINISHED ERROR in Plesk.

Are you facing Plesk DNSPROBE FINISHED ERROR ? We can help you.

Plesk is a commercial web hosting and server data center automation software with a control panel for Linux and Windows-based retail hosting service providers.

Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to fix related Plesk issues.

Nature of Plesk DNSPROBE FINISHED ERROR

This error can happen as a result of the following:

1. We cannot access domains hosted on the Plesk server since it shows error in a browser like this: 

DNSPROBE FINISHED ERROR

2. The domain cannot resolve locally with explicitly specified NS:

# dig +short exampe.com @ns1.example.com
#

3. Dist-upgrade to Ubuntu 20 may be performed recently.

Generally, this error can occur as a result a BIND misconfiguration.

You can see a sample of the error message:

# systemctl status bind9
* named.service – BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/bind9.service.d
`-respawn.conf
Active: active (running) since Sat 2020-10-03 02:18:00 GMT; 20min ago
. . .
`-236526 /usr/sbin/named -f -u bind

How to fix Plesk DNSPROBE FINISHED ERROR ?

1. Initially, we connect to the server via SSH.

2. Then we edit /etc/default/named config file. Here, we replace the OPTIONS parameter.

Before:

# cat /etc/default/named
. . .
OPTIONS="-u bind"

After:

# cat /etc/default/named
. . .
OPTIONS=" -t /var/named/run-root -c /etc/named.conf -u bind -n 2"

3. Eventually, we restart the BIND service:

# systemctl restart bind9​

4. Finally, we repair DNS for domains:

# plesk repair dns

This should fix the error.

[Need to fix Plesk issues ? We can help you. ]