1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

BIND not starting in PLESK 7.5.4 on CentOS 4.2 server

Discussion in 'Plesk for Linux - 8.x and Older' started by mgnetuk06, Jan 31, 2006.

  1. mgnetuk06

    mgnetuk06 Guest

    0
     
    Hi all.

    First post here.

    I have a CentOS 4.2 box running PLESK 7.5.4. Everything works fine except BIND/DNS. The 'BIND' service refuses to start from within PLESK. I have tried to start it manually from the terminal using:

    # service named start

    results in

    # started [OK]

    message. However, when I issue the

    # service named status

    command, I get the following error message:

    # service named status
    rndc: connect failed: connection refused

    BIND does not appear to be working, although it says it starts OK.

    I downloaded CentOS 4.2 from the CentOS download web site, burned the ISO to CD, did a minimal install, and installed direct from the PLESK server. I have the latest versions of most packages.

    Any help appreciated.

    Kind regards,

    MGNETUK06
     
  2. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Check the /var/log/messages file for clues
     
  3. Kanagaraj

    Kanagaraj Basic Pleskian

    24
    23%
    Joined:
    May 19, 2003
    Messages:
    60
    Likes Received:
    0
    I have same, Please follow the steps,

    Regards
    Kanagaraj

    About DNS: it is well know problem between Plesk and SeLinux secure police. You should set selinux in permissive or disabled mode and reboot your server:
    [root@server ~]# cat /etc/sysconfig/selinux # This file controls the state of SELinux on the system.
    # SELINUX= can take one of these three values:
    # enforcing - SELinux security policy is enforced.
    # permissive - SELinux prints warnings instead of enforcing.
    # disabled - SELinux is fully disabled.
    SELINUX=enforcing
    # SELINUXTYPE= type of policy in use. Possible values are:
    # targeted - Only targeted network daemons are protected.
    # strict - Full SELinux protection.
    SELINUXTYPE=targeted
     
Loading...