Articles in this section

Websites hosted in Plesk are not accessible when the DNS server is stopped

Kuzma Ivanov
Updated
Plesk for Linux kb: technical ABT: Group A

Applicable to:

  • Plesk for Linux

Symptoms

  • Websites hosted in Plesk are not accessible.

  • DNS zones are not synchronized via the Slave DNS Manager extension.

  • It is not possible to telnet to the server locally on port 53:

  • # telnet localhost 53
    Trying ::1...
    telnet: connect to address ::1: Connection refused
    Trying 127.0.0.1...
    telnet: connect to address 127.0.0.1: Connection refused

Cause

The DNS Server (BIND) service is stopped in Plesk at Tools & Settings > Services Management:


Screenshot_2019-09-28_Services_-_Plesk_Onyx_17_8_11.png

Resolution

Start the DNS Server (BIND) service:

  1. In Plesk, go to Tools & Settings > Services Management.

  2. Click the Screenshot_2020-11-16_Services_-_Plesk_Obsidian_18_0_30.png button next to the DNS Server (BIND) service.

 

Command=line instructions

 

  1. Connect to the Plesk server via SSH.

  2. Start the DNS server service:

    • on CentOS distributions:

      # service named-chroot start

    • on Debian/Ubuntu-based distributions:

      # service bind9 start

 

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.