The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

named not running!

Discussion in 'General Discussion' started by totalufo, Mar 6, 2002.

  1. totalufo

    totalufo Well-Known Member

    Joined:
    Jan 17, 2002
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    16
    When I try to restart bind, It starts ok but get the mesage

    &named not running&

    I also get this message while setting up an account in WHM:

    ndc: connect: connection refused


    So I decided to tail the message log and got this

    Mar 6 23:11:53 localhost named: named startup succeeded
    Mar 6 23:11:53 localhost named[22715]: loading configuration from '/etc/named.conf'
    Mar 6 23:11:53 localhost named[22715]: /etc/named.conf:25: parse error near file
    Mar 6 23:11:53 localhost named[22715]: loading configuration: failure
    Mar 6 23:11:53 localhost named[22715]: exiting (due to fatal error)

    So, I went into named.conf and went to line 25 and here's what I get.

    file &/var/named/teenieschoolgirls.com.db&;

    here's the entire named.conf
    If you'll notice where it shows the name servers, it has them as &type slave&

    When my client set up his name server, he accidently put his name server address in the master name server field. I have a feeling, this is what is causing the problem.

    // generated by named-bootconf.pl

    options {
    directory &/var/named&;
    /*
    * If there is a firewall between you and nameservers you want
    * to talk to, you might need to uncomment the query-source
    * directive below. Previous versions of BIND always asked
    * questions using port 53, but BIND 8.1 uses an unprivileged
    * port by default.
    */
    // query-source address * port 53;
    };

    //
    // a caching only nameserver config
    //
    controls {
    inet 127.0.0.1 allow { localhost; } keys { rndckey; };
    };



    include &/etc/rndc.key&;
    file &/var/named/teenieschoolgirls.com.db&;
    };
    zone &.& IN {
    type hint;
    file &named.ca&;
    };

    zone &0.0.127.in-addr.arpa& IN {


    zone &0.0.127.in-addr.arpa& IN {
    type slave;
    masters {
    NS1.TEENIESCHOOLGIRLS.COM,;
    };
    file &named.local&;
    allow-update { none; };
    };

    zone &localhost& IN {
    type slave;
    masters {
    NS1.TEENIESCHOOLGIRLS.COM,;
    };
    file &localhost.zone&;
    allow-update { none; };
    };

    zone &teenieschoolgirls.com& {
    type master;
    file &/var/named/teenieschoolgirls.com.db&;
    };
    zone &mylingeriefetish.com& {
    type master;
    file &/var/named/mylingeriefetish.com.db&;
    };
    zone &sluttysoccermoms.com& {
    type master;
    file &/var/named/sluttysoccermoms.com.db&;
    };
    zone &youngteensinuniform.com& {

    };
    zone &youngteensinuniform.com& {
    type master;
    file &/var/named/youngteensinuniform.com.db&;
    };
    zone &tes.com& {
    type master;
    file &/var/named/tes.com.db&;
    };
    zone &test2.com& {
    type master;
    file &/var/named/test2.com.db&;
    };



    Any Ideas?
     
  2. WeinBar

    WeinBar Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Is that your named.conf file?


    There are quite a few errors. Try running /scripts/cleandns8
     
  3. totalufo

    totalufo Well-Known Member

    Joined:
    Jan 17, 2002
    Messages:
    160
    Likes Received:
    0
    Trophy Points:
    16
    no luck. Did not work
     
  4. jumpdomain

    jumpdomain Well-Known Member

    Joined:
    Aug 12, 2001
    Messages:
    109
    Likes Received:
    0
    Trophy Points:
    16
    You can try this script:
    /scripts/unslavenamedconf

    However, your named.conf is in bad shape... You probably need to clean it up manually...
     
Loading...

Share This Page