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 stops working and named.conf empty

Discussion in 'General Discussion' started by Snowman30, Nov 9, 2005.

  1. Snowman30

    Snowman30 Well-Known Member
    PartnerNOC

    Joined:
    Apr 7, 2002
    Messages:
    681
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    DataCenter Provider
    Ive just seen a very weird issue across all of our servers which are setup the same way and running R30

    named was still showing to be working but everyones nameservers appear to be lame and so sites stopped working

    a check of named.conf shows all the domains missing

    ive had to run

    /scripts/fixndc
    /scripts/rebuildnamedconf
    and restart named to get the sites back online.

    Is this a known bug in the current Release?

    Anyone know why it would be happening?
     
  2. theprimehost

    theprimehost Active Member

    Joined:
    Nov 24, 2002
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    Same here on one of our servers...
     
  3. theprimehost

    theprimehost Active Member

    Joined:
    Nov 24, 2002
    Messages:
    29
    Likes Received:
    0
    Trophy Points:
    1
    Nevermind...fixed it.

    /scripts/rebuildnamedconf

    then restarting named corrected it for us.
     
  4. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    It happens because you have installed the caching-nameserver rpm which provides a simply configured named.conf whenever that rpm is updated. To avoid the problem in the future, add caching-nameserver* to your yum or up2date exclude list.
     
  5. CoolMike

    CoolMike Well-Known Member

    Joined:
    Sep 6, 2001
    Messages:
    307
    Likes Received:
    0
    Trophy Points:
    16
    Thanks for the infos, I had exactly the same problem. What else should be in this line? My exlude line looks now like this:

    exclude=httpd* mysql* php* perl* mod_ssl* kernel* spamassassin* caching-nameserver*

    Michael
     
  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
    I currently use the following, I wouldn't recommend using perl* anymore and would stick to just perl otherwise you can have problems installing other rpms that have perl module dependencies:

    exclude=courier* mysql* spamassassin* httpd* perl mysql* php* mod_ssl* imap* squirrelmail* caching-nameserver* kernel*
     
  7. jcn

    jcn Well-Known Member

    Joined:
    Sep 17, 2003
    Messages:
    56
    Likes Received:
    0
    Trophy Points:
    6
    Hey, thanks for the tip, this happened to me last night too: I added a new domain and completely wiped out the named.conf file except for the caching-nameserver's named.conf + the new domain I just added.

    Besides adding caching-nameserver to the yum exclusions, do I also have to

    a) remove that package and
    b) remove any template files that may be causing problems?

    Or should just adding the exclusion be enough?

    Thanks!
     
  8. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    You only need to add it to the exclusion/pkgskip list.
     
  9. jcn

    jcn Well-Known Member

    Joined:
    Sep 17, 2003
    Messages:
    56
    Likes Received:
    0
    Trophy Points:
    6
    Very cool. Thanks.
     
  10. denisdekat09

    denisdekat09 Well-Known Member

    Joined:
    Mar 2, 2002
    Messages:
    265
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    San Francisco
    I am trying all of this on one server and the rebuildnamedconf is not helping. /etc/named.conf is totally emtpy :(

    Any ideas on hwo to rebuild named.conf?

    Thanks :)
     
Loading...

Share This Page