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.

Bind Issue *please help*

Discussion in 'Bind / DNS / Nameserver Issues' started by NH-Benjamin, Aug 18, 2004.

  1. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Odd issue..... we just setup a new WHM box and for some reason bind seems to be fooked... its not storing records and when we restart it it outputs the following..... its a fresh WHM install....any help would be great.


    named started ok Aug 18 02:09:54 localhost named[10337]: invalid command from 127.0.0.1#46954: bad auth Aug 18 02:09:54 localhost named[10337]: shutting down Aug 18 02:09:54 localhost named[10337]: stopping command channel on 127.0.0.1#953 Aug 18 02:09:54 localhost named[10337]: no longer listening on 127.0.0.1#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.55#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.50#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.41#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.44#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.218#53 Aug 18 02:09:54 localhost named[10337]: exiting Aug 17 23:09:54 localhost named: named shutdown succeeded Aug 18 02:09:54 localhost named[10556]: starting BIND 9.2.2-P3 -u named -t /var/named/chroot Aug 18 02:09:54 localhost named[10556]: using 1 CPU Aug 18 02:09:54 localhost named[10556]: loading configuration from '/etc/named.conf' Aug 18 02:09:54 localhost named[10556]: no IPv6 interfaces found Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0, *.*.*.55#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:1, *.*.*.50#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:2, *.*.*.41#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:3, *.*.*.44#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:4, *.*.*.218#53 Aug 18 02:09:54 localhost named[10556]: command channel listening on 127.0.0.1#953 Aug 18 02:09:54 localhost named[10556]: running Aug 17 23:09:54 localhost named: named startup succeeded
     
  2. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    also WHM isnt showing any zones
     
  3. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    any help? cpanel isnt anwsering ticket :(
     
  4. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    What is your OS?
     
  5. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Fedora Core 1
     
  6. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    FC1 sets up bind in a chroot jail which doesn't work for cPanel. Comment out the following in /etc/sysconfig/named

    # ROOTDIR=/var/named/chroot

    Then restart bind.
     
  7. vivek

    vivek Well-Known Member

    Joined:
    Mar 2, 2004
    Messages:
    93
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    India
    Hello,

    If you are not able to bind then follow the steps bellow
    You can try out this :

    Solution :To bind/add the IP Address follow these step:

    step 1 :: #cd /etc/sysconfig /network-scripts

    step 2 :: #cp ifcfg-eth0 ifcfg-eth0:0

    step 3 :: #vi ifcfg-eth0:0
    <then replace these things only: device = eth0 by eth0:0 & IPadd = <your Ip Add>. Dont change rest of the things Save the changes & quit from the file >.

    step 4 :: #service network restart

    step 5 :: #ifup eth0:0

    This will bind/add the Ipadd to your NIC card (or you can say to your server).

    If you still face the problem then paste the error so that i can guide you.
    Or you can mail me.


    Thank You.
    Vivek
    Support Team. :D
     
  8. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    I did has you directed and now its listing zones in WHM but the error i pasted in my initial post is still output upon retstart of bind and its not a kosher error message for a production enviroment so I need to figure out whats causing the error message.
     
  9. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    Is it just outputting a bunch of "sending notifies" messages? If so, that's normal.
     
  10. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    It's outputting the error message in my initial post each time i restart bind initially WHM wasnt listing zones but i got that fixed but the error message is still there.


    named started ok Aug 18 02:09:54 localhost named[10337]: invalid command from 127.0.0.1#46954: bad auth Aug 18 02:09:54 localhost named[10337]: shutting down Aug 18 02:09:54 localhost named[10337]: stopping command channel on 127.0.0.1#953 Aug 18 02:09:54 localhost named[10337]: no longer listening on 127.0.0.1#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.55#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.50#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.41#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.44#53 Aug 18 02:09:54 localhost named[10337]: no longer listening on *.*.*.218#53 Aug 18 02:09:54 localhost named[10337]: exiting Aug 17 23:09:54 localhost named: named shutdown succeeded Aug 18 02:09:54 localhost named[10556]: starting BIND 9.2.2-P3 -u named -t /var/named/chroot Aug 18 02:09:54 localhost named[10556]: using 1 CPU Aug 18 02:09:54 localhost named[10556]: loading configuration from '/etc/named.conf' Aug 18 02:09:54 localhost named[10556]: no IPv6 interfaces found Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0, *.*.*.55#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:1, *.*.*.50#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:2, *.*.*.41#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:3, *.*.*.44#53 Aug 18 02:09:54 localhost named[10556]: listening on IPv4 interface eth0:4, *.*.*.218#53 Aug 18 02:09:54 localhost named[10556]: command channel listening on 127.0.0.1#953 Aug 18 02:09:54 localhost named[10556]: running Aug 17 23:09:54 localhost named: named startup succeeded


    If thats normal I must be odd because we have a handful of WHM boxes and we never get the error above on them. Any assistance regarding this error and how to fix/get rid of it would be great.
     
  11. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    No, that's not normal. You have 8 posts, so I assumed you were a newbie. Sorry. Try running this command from shell and see if that fixes it:

    named -u named -g
     
  12. vivek

    vivek Well-Known Member

    Joined:
    Mar 2, 2004
    Messages:
    93
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    India
    Hello,
    I have newly registered on cpanel, but i am regular surfer of lots of forums specially ev1servers.com If you dont belive me than check on forums.ev1servers.net.
    you can view lot of posts on this forums.
    Now its upto you to consider my help.

    Thank You.
    Vivek
     
  13. kctalk

    kctalk Registered

    Joined:
    Aug 18, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    I work with him and I will try the resolutions suggested and post the results shortly. For being a newbie to the forum, I personally do not care much if you are new as long as you can help with the problems posted here :) Welcome to the forums here, and thank you for your assistance.

    I will notify everyone if issues still remain after attempting the resoulutions provided above....
     
  14. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    root@pacific [~]# cd /etc/sysconfig /network-scripts
    root@pacific [/etc/sysconfig]# cp ifcfg-eth0 ifcfg-eth0:0
    cp: cannot stat `ifcfg-eth0': No such file or directory
    root@pacific [/etc/sysconfig]#
     
  15. adapter

    adapter Well-Known Member
    PartnerNOC

    Joined:
    Sep 17, 2003
    Messages:
    391
    Likes Received:
    0
    Trophy Points:
    16
    Hi

    did u fix this problem? i get the same notification when i restart bind
     
  16. NH-Benjamin

    NH-Benjamin Member

    Joined:
    Jun 4, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    nope =/ not yet I wonder whats up
     
  17. vivek

    vivek Well-Known Member

    Joined:
    Mar 2, 2004
    Messages:
    93
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    India
    Hello,

    Then there should be some investigation, need to place ticket. The concern techs will help you out.
    But as per my knowledge and experience of mine it should work. Let see any other expertise resond to the post.

    Thank You.
    Vivek
     
Loading...

Share This Page