Plesk DNSPROBE FINISHED ERROR | Fixed

Plesk DNSPROBE FINISHED ERROR stuck on your screen? You can rely on us.

Most frequently, this error can be caused by BIND misconfiguration.

We help our clients with a variety of Plesk inquiries as part of our server management services.

Let's talk about this error's symptoms, cause, and solution.

Plesk DNSPROBE FINISHED ERROR

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

Let's look at an error that could occur while using Plesk.

These are the main signs of this error:

• We are unable to access domains hosted on the Plesk server because the following error is displayed in the browser:

DNSPROBE FINISHED ERROR

• The domain cannot be locally resolved with the given NS:

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

• Dist-upgrade to Ubuntu 20 might have recently been done.

According to our support technicians, a BIND misconfiguration is typically to blame for this.

Optional gaps could exist, as shown below:

# 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

We will concentrate on the solution now that we have seen the cause and symptoms. Let's talk about a simple and effective way to correct the mistake right now.

How can the problem be fixed?

Let's proceed and see what our support technicians do to correct this error.

1. We initially use SSH to connect to the server.

2. The /etc/default/named config file is then edited. In this case, we swap out the OPTIONS parameter.

# 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. We eventually restart the BIND service:

# systemctl restart bind9​

4. Last but not least, we fix DNS for domains:

# plesk repair dns

Conclusion

In conclusion, BIND misconfiguration can result in a Plesk DNSPROBE FINISHED ERROR. Today, we witnessed the error being fixed for our clients by our Support Techs.