Named crashing every 20 min

Discussion in 'Installation/Configuration' started by RingofFire, Nov 21, 2006.

  1. RingofFire

    RingofFire New Member

    Im not sure if its something I did in ISPconfig, but bind is crashing every 20 min.

    Heres the log from named.run:

    Code:
    zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
    zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
    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/localhost_resolver: loaded serial 1997022700
    zone localdomain/IN/localhost_resolver: loaded serial 42
    zone localhost/IN/localhost_resolver: loaded serial 42
    running
    shutting down: flushing changes
    stopping command channel on 127.0.0.1#953
    no longer listening on 127.0.0.1#53
    exiting
    zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42
    zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700
    zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42
    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/localhost_resolver: loaded serial 1997022700
    zone localdomain/IN/localhost_resolver: loaded serial 42
    zone localhost/IN/localhost_resolver: loaded serial 42
    running
    shutting down: flushing changes
    stopping command channel on 127.0.0.1#953
    no longer listening on 127.0.0.1#53
    exiting
    
    From:
    var/log/messages
    Code:
    Nov 20 17:38:41 svr named: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    Nov 20 17:38:41 svr named: zone 77.210.207.in-addr.arpa/IN: loaded serial 2006102602
    Nov 20 17:38:41 svr named: zone 53.254.65.in-addr.arpa/IN: loaded serial 2006111802
    Nov 20 17:38:41 svr named: zone appalhost.info/IN: loaded serial 2006101602
    Nov 20 17:38:41 svr named: zone test.appalhost.info/IN: loaded serial 2006102602
    Nov 20 17:38:41 svr named: dns_master_load: pri.xenotype.net:18: www.xenotype.net: CNAME and other data
    Nov 20 17:38:41 svr named: dns_master_load: pri.xenotype.net:18: www.xenotype.net: CNAME and other data
    Nov 20 17:38:41 svr named: zone xenotype.net/IN: loading master file pri.xenotype.net: CNAME and other data
    Nov 20 17:38:41 svr named: _default/xenotype.net/IN: CNAME and other data
    Nov 20 17:40:53 svr proftpd[28499]: localhost (127.0.0.1[127.0.0.1]) - FTP session closed.
    Nov 20 17:40:57 svr named: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
    Nov 20 17:40:57 svr named: zone 77.210.207.in-addr.arpa/IN: loaded serial 2006112001
    Nov 20 17:40:57 svr named: zone 53.254.65.in-addr.arpa/IN: loaded serial 2006111802
    Nov 20 17:40:57 svr named: zone appalhost.info/IN: loaded serial 2006101602
    Nov 20 17:40:57 svr named: zone test.appalhost.info/IN: loaded serial 2006102602
    Nov 20 17:40:57 svr named: dns_master_load: pri.xenotype.net:18: www.xenotype.net: CNAME and other data
    Nov 20 17:40:57 svr named: dns_master_load: pri.xenotype.net:18: www.xenotype.net: CNAME and other data
    Nov 20 17:40:57 svr named: zone xenotype.net/IN: loading master file pri.xenotype.net: CNAME and other data
    Nov 20 17:40:57 svr named: _default/xenotype.net/IN: CNAME and other data
    Nov 20 17:40:57 svr named: zone testtester.com/IN: loaded serial 2006112001
    Nov 20 17:47:16 svr proftpd[3913]: localhost (127.0.0.1[127.0.0.1]) - FTP session opened.
    

    Domains I have running are xenotype.net(which I just purchased), appalhost.info, nameservers are ns1.appalhost.info, ns2.appalhost.info

    The test domain I created to check things, its not real.

    Ips are 207.210.77.119 and 65.254.53.154. Xenotype is hosted on the 65 address, 207 is for appalhost.info.

    I was trying to solve a problem with my registrar and I added a bad CNAME for the xenotype.net domain. I deleted it in the primary zone file in bind chroot, but couldnt figure out how to delete it in ispconfig.

    What could be causing the crash? Is it anything to worry about? Is this normal?
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    I cant see no crashs in your log, only normal shutdowns. Does your named crash when you restart it with the script in /etc/init.d/ ?

    Open the domain xenotype.net in ISPConfig and delete the cname record, then wait a minute and empty the recycle bin. Deleteing a cname manually in a zone file will be overridden by ISPConfig.
     
  3. RingofFire

    RingofFire New Member

    deleted it manually in phpmyadmin

    I have ispconfig set so it notifies me if anything goes down.

    Could the bad cname be causing bind to shut down and restart? Because I didnt do anything to cause it to do that.

    I also updated bind and a few other things with yum, could that be causing it?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    That was a really bad idea, beacuse deleting records manually with phpmyadmin will corrupt your database when you dont delete the corresponding records in dns_nodes and dns_dep. Thtats why I told you to delete it in the interface and not in phpmyadmin.
     
  5. RingofFire

    RingofFire New Member

    I deleted the domain and its records and created it again with backed up data.

    It appears to be 100% fixed.
     

Share This Page