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.

please help :(( bind failed

Discussion in 'Bind / DNS / Nameserver Issues' started by kaveh_cdeb, Jan 9, 2005.

  1. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    hi
    bind failed and when I want to restart it from whm this message shown


    Attempting to restart named
    Waiting for named to restart.... . . . . . . . . . . finished.

    named status named 29017 0.1 0.2 46464 2900 ? S 01:40 0:00 /usr/sbin/named -u named



    named started ok Jan 10 01:40:23 ns1 named[15631]: shutting down Jan 10 01:40:23 ns1 named[15631]: no longer listening on 127.0.0.1#53 Jan 10 01:40:23 ns1 named[15631]: no longer listening on 67.19.81.26#53 Jan 10 01:40:23 ns1 named[15631]: no longer listening on 67.19.81.27#53 Jan 10 01:40:23 ns1 named[15631]: no longer listening on 67.19.81.28#53 Jan 10 01:40:23 ns1 named[15631]: no longer listening on 67.19.81.29#53 Jan 10 01:40:23 ns1 named[15631]: no longer listening on 67.19.81.30#53 Jan 10 01:40:23 ns1 named[15631]: exiting Jan 10 01:40:23 ns1 named: named shutdown succeeded Jan 10 01:40:24 ns1 named[29017]: starting BIND 9.2.4 -u named Jan 10 01:40:24 ns1 named[29017]: using 2 CPUs Jan 10 01:40:24 ns1 named[29017]: loading configuration from '/etc/named.conf' Jan 10 01:40:24 ns1 named[29017]: no IPv6 interfaces found Jan 10 01:40:24 ns1 named[29017]: listening on IPv4 interface lo, 127.0.0.1#53 Jan 10 01:40:24 ns1 named[29017]: listening on IPv4 interface eth0, 67.19.81.26#53 Jan 10 01:40:24 ns1 named[29017]: listening on IPv4 interface eth0:1, 67.19.81.27#53 Jan 10 01:40:24 ns1 named[29017]: listening on IPv4 interface eth0:2, 67.19.81.28#53 Jan 10 01:40:24 ns1 named: named startup succeeded Jan 10 01:40:24 ns1 named[29017]: listening on IPv4 interface eth0:3, 67.19.81.29#53 Jan 10 01:40:24 ns1 named[29017]: listening on IPv4 interface eth0:4, 67.19.81.30#53 Jan 10 01:40:24 ns1 named[29017]: /etc/named.conf:23: couldn't install keys for command channel 127.0.0.1#953: not found Jan 10 01:40:24 ns1 named[29017]: /etc/named.conf:23: couldn't add command channel 127.0.0.1#953: not found Jan 10 01:40:24 ns1 named[29017]: zone 0.in-addr.arpa/IN: loaded serial 42 Jan 10 01:40:24 ns1 named[29017]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 Jan 10 01:40:24 ns1 named[29017]: zone 255.in-addr.arpa/IN: loaded serial 42 Jan 10 01:40:24 ns1 named[29017]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700 Jan 10 01:40:24 ns1 named[29017]: zone localdomain/IN: loaded serial 42 Jan 10 01:40:24 ns1 named[29017]: zone localhost/IN: loaded serial 42 Jan 10 01:40:24 ns1 named[29017]: running

    please help me :mad: :confused: :(

    ps : choose a zone to edit box is empty :(
     
  2. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    Run:
    /scripts/fixndc
    /scripts/fixnamed
     
  3. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
  4. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    help please :(( :( :mad:
     
  5. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    If you have a firewall running, disable it and try running /scripts/updatenow and /scripts/upcp. It seems that the mirror is blocked by your firewall.
     
  6. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    thanks again

    i disabled APF

    but nothing changed

    then when i tried to restart the APF i get this message

    root@ns1 [/]# /etc/apf/apf -s
    iptables v1.2.8: host/network `254.67-18-185.reverse.theplanet.com' not found
    Try `iptables -h' or 'iptables --help' for more information.
    iptables v1.2.8: host/network `254.67-18-185.reverse.theplanet.com' not found
    Try `iptables -h' or 'iptables --help' for more information.
    iptables v1.2.8: host/network `103.138.182.65.in-addr.arpa' not found
    Try `iptables -h' or 'iptables --help' for more information.
    iptables v1.2.8: host/network `103.138.182.65.in-addr.arpa' not found
    Try `iptables -h' or 'iptables --help' for more information.


    :(
     
  7. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    APF can't block by DNS, so you need to edit /etc/apf/deny_hosts.rules and replace the reverse DNS records with their IP.

    As for the bind and cpanel stuff...I'm at a loss atm.
     
  8. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    thank slot

    the apf is ok now

    but i still have the dns problem + update problem :(
     
  9. Blue|Fusion

    Blue|Fusion Well-Known Member

    Joined:
    Sep 12, 2004
    Messages:
    378
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Cleveland, Ohio
    OK...

    For updating... It seems the stable tree is not there atm (being updated to new build perhaps)?

    But I suggest using RELEASE or CURRENT. I've been running CURRENT with no problems. Change that in the update config, then run upcp.
     
  10. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6

    maybe

    but the other updates is broken too

    in example no module installs
    with the same error

    or

    /scripts/updatenow

    /scripts/easyapache

    with the same upcp error
     
  11. philb

    philb Well-Known Member

    Joined:
    Jan 28, 2004
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    try:

    rm /var/cpanel/version/9.9.9.1

    /scripts/upcp
     
  12. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    thanks philb and thanks Blue|Fusion

    the update is ok now

    but the dns error is still there

    my clients will kill me :eek: :(

    please help :(
     
  13. philb

    philb Well-Known Member

    Joined:
    Jan 28, 2004
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    please try running

    /scripts/fixnamed
    /scripts/fixndc

    again and see if it works now when you type

    rndc reload

    if not, paste the error here, also do

    tail -n 1000 /var/log/messages | grep named

    and paste them in here too
     
  14. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    thanks philb

    all commands i checked
    but dont helped

    and the result of the last command that you suggested me is too larg and im using putty . :D

    you know putty missing some larg results under the scroll
    but a part of message that can be seen is it :
    (in 'elham85.com'?): 67.19.81.26#53
    Jan 10 04:33:43 ns1 named[25519]: shutting down: flushing changes
    Jan 10 04:33:43 ns1 named[25519]: stopping command channel on 127.0.0.1#953
    Jan 10 04:33:43 ns1 named[25519]: no longer listening on 127.0.0.1#53
    Jan 10 04:33:43 ns1 named[25519]: no longer listening on 67.19.81.26#53
    Jan 10 04:33:43 ns1 named[25519]: no longer listening on 67.19.81.27#53
    Jan 10 04:33:43 ns1 named[25519]: no longer listening on 67.19.81.28#53
    Jan 10 04:33:43 ns1 named[25519]: no longer listening on 67.19.81.29#53
    Jan 10 04:33:43 ns1 named[25519]: no longer listening on 67.19.81.30#53
    Jan 10 04:33:43 ns1 named[25519]: exiting
    Jan 10 04:33:43 ns1 named: succeeded
    Jan 10 04:33:43 ns1 named[16639]: starting BIND 9.2.4 -u named
    Jan 10 04:33:43 ns1 named[16639]: using 2 CPUs
    Jan 10 04:33:43 ns1 named[16639]: loading configuration from '/etc/named.conf'
    Jan 10 04:33:43 ns1 named[16639]: no IPv6 interfaces found
    Jan 10 04:33:43 ns1 named[16639]: listening on IPv4 interface lo, 127.0.0.1#53
    Jan 10 04:33:43 ns1 named[16639]: listening on IPv4 interface eth0, 67.19.81.26#53
    Jan 10 04:33:43 ns1 named[16639]: listening on IPv4 interface eth0:1, 67.19.81.27#53
    Jan 10 04:33:43 ns1 named[16639]: listening on IPv4 interface eth0:2, 67.19.81.28#53
    Jan 10 04:33:43 ns1 named[16639]: listening on IPv4 interface eth0:3, 67.19.81.29#53
    Jan 10 04:33:43 ns1 named[16639]: listening on IPv4 interface eth0:4, 67.19.81.30#53
    Jan 10 04:33:43 ns1 named[16639]: command channel listening on 127.0.0.1#953
    Jan 10 04:33:43 ns1 named[16639]: zone 0.in-addr.arpa/IN: loaded serial 42
    Jan 10 04:33:43 ns1 named: named startup succeeded
    Jan 10 04:33:43 ns1 named[16639]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    Jan 10 04:33:43 ns1 named[16639]: zone 255.in-addr.arpa/IN: loaded serial 42
    Jan 10 04:33:43 ns1 named[16639]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
    Jan 10 04:33:43 ns1 named[16639]: zone localdomain/IN: loaded serial 42
    Jan 10 04:33:43 ns1 named[16639]: zone localhost/IN: loaded serial 42
    Jan 10 04:33:43 ns1 named[16639]: running
    Jan 10 04:48:53 ns1 named[16639]: lame server resolving 'elham85.com' (in 'elham85.com'?): 67.19.81.26#53
    Jan 10 04:48:53 ns1 named[16639]: lame server resolving 'elham85.com' (in 'elham85.com'?): 67.19.81.27#53
    Jan 10 04:48:53 ns1 named[16639]: lame server resolving 'elham85.com' (in 'elham85.com'?): 67.19.81.26#53
    Jan 10 04:48:53 ns1 named[16639]: lame server resolving 'elham85.com' (in 'elham85.com'?): 67.19.81.27#53
    Jan 10 04:49:05 ns1 named[16639]: shutting down: flushing changes
    Jan 10 04:49:05 ns1 named[16639]: stopping command channel on 127.0.0.1#953
    Jan 10 04:49:05 ns1 named[16639]: no longer listening on 127.0.0.1#53
    Jan 10 04:49:05 ns1 named[16639]: no longer listening on 67.19.81.26#53
    Jan 10 04:49:05 ns1 named[16639]: no longer listening on 67.19.81.27#53
    Jan 10 04:49:05 ns1 named[16639]: no longer listening on 67.19.81.28#53
    Jan 10 04:49:05 ns1 named[16639]: no longer listening on 67.19.81.29#53
    Jan 10 04:49:05 ns1 named[16639]: no longer listening on 67.19.81.30#53
    Jan 10 04:49:05 ns1 named[16639]: exiting
    Jan 10 04:49:05 ns1 named: succeeded
    Jan 10 04:49:05 ns1 named[17018]: starting BIND 9.2.4 -u named
    Jan 10 04:49:05 ns1 named[17018]: using 2 CPUs
    Jan 10 04:49:05 ns1 named[17018]: loading configuration from '/etc/named.conf'
    Jan 10 04:49:05 ns1 named: named startup succeeded
    Jan 10 04:49:05 ns1 named[17018]: no IPv6 interfaces found
    Jan 10 04:49:05 ns1 named[17018]: listening on IPv4 interface lo, 127.0.0.1#53
    Jan 10 04:49:05 ns1 named[17018]: listening on IPv4 interface eth0, 67.19.81.26#53
    Jan 10 04:49:05 ns1 named[17018]: listening on IPv4 interface eth0:1, 67.19.81.27#53
    Jan 10 04:49:05 ns1 named[17018]: listening on IPv4 interface eth0:2, 67.19.81.28#53
    Jan 10 04:49:05 ns1 named[17018]: listening on IPv4 interface eth0:3, 67.19.81.29#53
    Jan 10 04:49:05 ns1 named[17018]: listening on IPv4 interface eth0:4, 67.19.81.30#53
    Jan 10 04:49:05 ns1 named[17018]: command channel listening on 127.0.0.1#953
    Jan 10 04:49:05 ns1 named[17018]: zone 0.in-addr.arpa/IN: loaded serial 42
    Jan 10 04:49:05 ns1 named[17018]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    Jan 10 04:49:05 ns1 named[17018]: zone 255.in-addr.arpa/IN: loaded serial 42
    Jan 10 04:49:05 ns1 named[17018]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
    Jan 10 04:49:05 ns1 named[17018]: zone localdomain/IN: loaded serial 42
    Jan 10 04:49:05 ns1 named[17018]: zone localhost/IN: loaded serial 42
    Jan 10 04:49:05 ns1 named[17018]: running
    Jan 10 04:59:15 ns1 named[17018]: shutting down: flushing changes
    Jan 10 04:59:15 ns1 named[17018]: stopping command channel on 127.0.0.1#953
    Jan 10 04:59:15 ns1 named[17018]: no longer listening on 127.0.0.1#53
    Jan 10 04:59:15 ns1 named[17018]: no longer listening on 67.19.81.26#53
    Jan 10 04:59:15 ns1 named[17018]: no longer listening on 67.19.81.27#53
    Jan 10 04:59:15 ns1 named[17018]: no longer listening on 67.19.81.28#53
    Jan 10 04:59:15 ns1 named[17018]: no longer listening on 67.19.81.29#53
    Jan 10 04:59:15 ns1 named[17018]: no longer listening on 67.19.81.30#53
    Jan 10 04:59:15 ns1 named[17018]: exiting
    Jan 10 04:59:15 ns1 named: succeeded
    Jan 10 04:59:15 ns1 named[17371]: starting BIND 9.2.4 -u named
    Jan 10 04:59:15 ns1 named[17371]: using 2 CPUs
    Jan 10 04:59:15 ns1 named[17371]: loading configuration from '/etc/named.conf'
    Jan 10 04:59:15 ns1 named[17371]: no IPv6 interfaces found
    Jan 10 04:59:15 ns1 named[17371]: listening on IPv4 interface lo, 127.0.0.1#53
    Jan 10 04:59:15 ns1 named[17371]: listening on IPv4 interface eth0, 67.19.81.26#53
    Jan 10 04:59:15 ns1 named[17371]: listening on IPv4 interface eth0:1, 67.19.81.27#53
    Jan 10 04:59:15 ns1 named[17371]: listening on IPv4 interface eth0:2, 67.19.81.28#53
    Jan 10 04:59:15 ns1 named[17371]: listening on IPv4 interface eth0:3, 67.19.81.29#53
    Jan 10 04:59:15 ns1 named[17371]: listening on IPv4 interface eth0:4, 67.19.81.30#53
    Jan 10 04:59:15 ns1 named[17371]: command channel listening on 127.0.0.1#953
    Jan 10 04:59:15 ns1 named: named startup succeeded
    Jan 10 04:59:15 ns1 named[17371]: zone 0.in-addr.arpa/IN: loaded serial 42
    Jan 10 04:59:15 ns1 named[17371]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    Jan 10 04:59:15 ns1 named[17371]: zone 255.in-addr.arpa/IN: loaded serial 42
    Jan 10 04:59:15 ns1 named[17371]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
    Jan 10 04:59:15 ns1 named[17371]: zone localdomain/IN: loaded serial 42
    Jan 10 04:59:15 ns1 named[17371]: zone localhost/IN: loaded serial 42
    Jan 10 04:59:15 ns1 named[17371]: running
    Jan 10 05:00:31 ns1 named[17371]: loading configuration from '/etc/named.conf'
    Jan 10 05:00:31 ns1 named[17371]: no IPv6 interfaces found
    Jan 10 05:02:15 ns1 named[17371]: loading configuration from '/etc/named.conf'
    Jan 10 05:02:15 ns1 named[17371]: no IPv6 interfaces found
    Jan 10 05:02:29 ns1 named[17371]: client 193.0.0.63#59110: bad zone transfer request: 'iran.ug/IN': non-authoritative zone (NOTAUTH)
    Jan 10 05:02:30 ns1 named[17371]: client 193.0.0.63#59111: bad zone transfer request: 'iran.ug/IN': non-authoritative zone (NOTAUTH)
     
  15. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    any idea ?

    now the dns zone edit is ok but bind is still down

    when i edit a dns zone

    the result is it :

    zone domain.XXX/IN: loaded serial 2005011002
    OK

    Bind reloading on ns1 using rndc zone: [domain.XXX]
    Error reloading bind on ns1: rndc: 'reload' failed: not found



    Zone Modified!
     
  16. philb

    philb Well-Known Member

    Joined:
    Jan 28, 2004
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    Your DNS server is running ok. If it's not answering properly for your domains, the zone files must have gotten corrupted or deleted somehow, or are not listed in your dns server's config file anymore.

    If you look in the file /etc/named.conf , do you see zone entries for all of your domains listed?

    If you type rndc status, how many zones does it say it has?
     
  17. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    thanks

    yes my domains zone corrupted and in the /etc/named.conf i have`nt any domain zone

    and when i ran /rndc status

    bash: /rndc: No such file or directory
     
  18. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    is there any backup of /etc/named.conf in server ?

    what must i do now ?
     
  19. philb

    philb Well-Known Member

    Joined:
    Jan 28, 2004
    Messages:
    116
    Likes Received:
    0
    Trophy Points:
    16
    rndc status doesn't have a / on it.

    You can look in /etc/ for files that start named.conf for possible backups you could fall back to.

    Are your zone files still present in /var/named ?
     
  20. kaveh_cdeb

    kaveh_cdeb Active Member

    Joined:
    Oct 20, 2004
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    thanks

    yes my zone files still in var/named

    its the result of rndc status without / :(

    root@ns1 [/]# rndc status
    bash: rndc: command not found

    how can i roll back the backup ?

    thanks
     
Loading...

Share This Page