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.

DNS / BIND Issues

Discussion in 'Bind / DNS / Nameserver Issues' started by dragonmatrix, Jul 30, 2006.

  1. dragonmatrix

    dragonmatrix Member

    Joined:
    Nov 14, 2003
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    My DNS server is not working, the named.conf is correct. When I start BIND in WHM I get this:

    named statusnamed 16108 0.0 0.6 36760 3048 ? Ssl 19:27 0:00 /usr/sbin/named -u named


    named started ok Jul 30 19:27:46 host named[15843]: shutting down: flushing changes Jul 30 19:27:46 host named[15843]: stopping command channel on 127.0.0.1#953 Jul 30 19:27:46 host named[15843]: no longer listening on 127.0.0.1#53 Jul 30 19:27:46 host named[15843]: no longer listening on 67.159.26.53#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.226#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.227#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.228#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.229#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.230#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.231#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.232#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.233#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.234#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.235#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.236#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.237#53 Jul 30 19:27:46 host named[15843]: no longer listening on 208.53.135.238#53 Jul 30 19:27:46 host named[15843]: exiting Jul 30 19:27:46 host named[16108]: starting BIND 9.3.1 -u named Jul 30 19:27:46 host named[16108]: found 1 CPU, using 1 worker thread Jul 30 19:27:46 host named[16108]: loading configuration from '/etc/named.conf' Jul 30 19:27:46 host named[16108]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0, 67.159.26.53#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:1, 208.53.135.226#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:2, 208.53.135.227#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:3, 208.53.135.228#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:4, 208.53.135.229#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:5, 208.53.135.230#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:6, 208.53.135.231#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:7, 208.53.135.232#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:8, 208.53.135.233#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:9, 208.53.135.234#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:10, 208.53.135.235#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:11, 208.53.135.236#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:12, 208.53.135.237#53 Jul 30 19:27:46 host named[16108]: listening on IPv4 interface eth0:13, 208.53.135.238#53 Jul 30 19:27:46 host named[16108]: command channel listening on 127.0.0.1#953 Jul 30 19:27:46 host named[16108]: zone 0.in-addr.arpa/IN: loaded serial 42 Jul 30 19:27:46 host named[16108]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 Jul 30 19:27:46 host named[16108]: zone 255.in-addr.arpa/IN: loaded serial 42 Jul 30 19:27:46 host named[16108]: 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 Jul 30 19:27:46 host named[16108]: zone clubmissy.com/IN: loaded serial 2006072502 Jul 30 19:27:46 host named[16108]: zone dragonstreams.com/IN: loaded serial 2006072903 Jul 30 19:27:46 host named[16108]: zone max80s.com/IN: loaded serial 2006072501 Jul 30 19:27:46 host named[16108]: zone unzippedshow.com/IN: loaded serial 2006072501 Jul 30 19:27:46 host named[16108]: zone znetradio.com/IN: loaded serial 2006072501 Jul 30 19:27:46 host named[16108]: zone localdomain/IN: loaded serial 42 Jul 30 19:27:46 host named[16108]: zone localhost/IN: loaded serial 42 Jul 30 19:27:46 host named[16108]: zone 20v.net/IN: loaded serial 2006073001 Jul 30 19:27:46 host named[16108]: zone ns1.20v.net/IN: loaded serial 2006072904 Jul 30 19:27:46 host named[16108]: zone ns2.20v.net/IN: loaded serial 2006072903 Jul 30 19:27:46 host named[16108]: zone stream.20v.net/IN: loaded serial 2006073001 Jul 30 19:27:47 host named[16108]: running Jul 30 19:27:47 host named[16108]: zone stream.20v.net/IN: sending notifies (serial 2006073001) Jul 30 19:27:47 host named[16108]: zone dragonstreams.com/IN: sending notifies (serial 2006072903) Jul 30 19:27:47 host named[16108]: zone clubmissy.com/IN: sending notifies (serial 2006072502) Jul 30 19:27:47 host named[16108]: zone max80s.com/IN: sending notifies (serial 2006072501) Jul 30 19:27:47 host named[16108]: zone unzippedshow.com/IN: sending notifies (serial 2006072501) Jul 30 19:27:47 host named[16108]: zone znetradio.com/IN: sending notifies (serial 2006072501) Jul 30 19:27:47 host named[16108]: zone ns2.20v.net/IN: sending notifies (serial 2006072903) Jul 30 19:27:47 host named[16108]: zone ns1.20v.net/IN: sending notifies (serial 2006072904) Jul 30 19:27:47 host named[16108]: zone 20v.net/IN: sending notifies (serial 2006073001) Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'stream.20v.net' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'dragonstreams.com' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone '20v.net' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'clubmissy.com' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'max80s.com' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'unzippedshow.com' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'znetradio.com' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'ns2.20v.net' Jul 30 19:27:47 host named[16108]: client 208.53.135.227#34450: received notify for zone 'ns1.20v.net'
     
  2. dropby23

    dropby23 Well-Known Member

    Joined:
    Jan 16, 2005
    Messages:
    155
    Likes Received:
    0
    Trophy Points:
    16
    try this hope it helps
    mv /etc/named.conf /etc/named.old
    /scripts/rebuildnamedconf > /etc/named.conf
    service named stop
    killall -9 named
    /scripts/fixndc
    /scripts/fixndc
     
  3. dragonmatrix

    dragonmatrix Member

    Joined:
    Nov 14, 2003
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Thanks, but that did not help........
     
  4. bijo

    bijo Well-Known Member

    Joined:
    Aug 21, 2004
    Messages:
    475
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    India
    Hello,

    Why do u think like that?. This is normal. I have tested your name server using dig and nslookup and also i can see some domains with out any error :)
     
  5. dragonmatrix

    dragonmatrix Member

    Joined:
    Nov 14, 2003
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    I have used an different name server to resolve the few sites on the server but 20v.net, it still will not resolve. It was working fine till a few days ago, then stopped.
     
  6. bijo

    bijo Well-Known Member

    Joined:
    Aug 21, 2004
    Messages:
    475
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    India
    Hello,

    It seems that, the issue with the zone file of that domain.
    Check the zone file of that domain, and set the correct A record. I hope It will help you
     
  7. dragonmatrix

    dragonmatrix Member

    Joined:
    Nov 14, 2003
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Seems all is correct but when named starts it says no longer listening on port #53,
     
  8. firedragon

    firedragon Registered

    Joined:
    Feb 1, 2006
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    fixed my problem

    Thanks dropby23:D
     
  9. MADLaker

    MADLaker Registered

    Joined:
    Feb 3, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Chicago
    Worked for me too, thanks!
     
Loading...

Share This Page