Stuck with Plesk DNSPROBE FINISHED ERROR? We can help you.
Mostly, BIND misconfiguration can lead us to this error.
As part of our Server Management Services, we assist our customers with several Plesk queries.
Today, let us discuss the symptoms, cause, and fix to this error.
Plesk DNSPROBE FINISHED ERROR
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.
In this article, let us see an error that may come our way while we use Plesk.
The major symptoms of this error are as follows:
- We cannot access domains hosted on the Plesk server since it shows error in a browser like this:
DNSPROBE FINISHED ERROR
- The domain cannot resolve locally with explicitly specified NS:
# dig +short exampe.com @ns1.example.com #
- Dist-upgrade to Ubuntu 20 may be performed recently
Generally, our Support Techs says, this can cause due to a BIND misconfiguration.
There can be missing options like 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
Now that we saw the cause and symptoms, we will focus on the fix. Here, let us discuss an easy and quick method to fix the error.
How to resolve the error?
Moving ahead, let us see the steps our Support Techs perform in order to fix this error.
- Initially, we connect to the server via SSH
- Then we edit /etc/default/named config file. Here, we replace the OPTIONS parameter.
# cat /etc/default/named . . . OPTIONS=”-u bind”
# cat /etc/default/named . . . OPTIONS=” -t /var/named/run-root -c /etc/named.conf -u bind -n 2″
- Eventually, we restart the BIND service:
# systemctl restart bind9
- Finally, we repair DNS for domains:
# plesk repair dns
This should fix the error.
[Failed to resolve? Feel free to contact us at anytime]
To conclude, Plesk DNSPROBE FINISHED ERROR can cause because of BIND misconfiguration. Today, we saw how our Support Techs fix this error for our customers.