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.

nameserver galore

Discussion in 'Bind / DNS / Nameserver Issues' started by jhair, Jun 29, 2005.

  1. jhair

    jhair Registered

    Joined:
    Mar 22, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    I have spent many hours searching the forums and google. So please don't anyone say try searching the forums.

    As you might be able to tell from the topic I am having some trouble with my nameserver (well I assume that is the problem.

    My Setup:
    IP Addresses:
    202.174.105.45
    202.174.105.46
    202.174.105.47
    202.174.105.48

    Main Shared Virtual Host IP -> 202.174.105.45
    ns1.orgenen.net - 202.174.105.47
    ns2.orgenen.net - 202.174.105.46


    Bind Output: named started ok Jun 30 12:23:07 host named[22482]: shutting down: flushing changes Jun 30 12:23:07 host named[22482]: stopping command channel on 127.0.0.1#953 Jun 30 12:23:07 host named[22482]: no longer listening on 127.0.0.1#53 Jun 30 12:23:07 host named[22482]: no longer listening on 202.174.105.45#53 Jun 30 12:23:07 host named[22482]: no longer listening on 202.174.105.46#53 Jun 30 12:23:07 host named[22482]: no longer listening on 202.174.105.47#53 Jun 30 12:23:07 host named[22482]: no longer listening on 202.174.105.48#53 Jun 30 12:23:07 host named[22482]: exiting Jun 30 12:23:07 host named: succeeded Jun 30 12:23:07 host named[22626]: starting BIND 9.2.4 -u named Jun 30 12:23:07 host named[22626]: using 4 CPUs Jun 30 12:23:07 host named[22626]: loading configuration from '/etc/named.conf' Jun 30 12:23:07 host named: named startup succeeded Jun 30 12:23:07 host named[22626]: listening on IPv4 interface lo, 127.0.0.1#53 Jun 30 12:23:07 host named[22626]: listening on IPv4 interface eth0, 202.174.105.45#53 Jun 30 12:23:07 host named[22626]: listening on IPv4 interface eth0:1, 202.174.105.46#53 Jun 30 12:23:07 host named[22626]: listening on IPv4 interface eth0:2, 202.174.105.47#53 Jun 30 12:23:07 host named[22626]: listening on IPv4 interface eth0:3, 202.174.105.48#53 Jun 30 12:23:07 host named[22626]: command channel listening on 127.0.0.1#953 Jun 30 12:23:07 host named[22626]: zone 0.in-addr.arpa/IN: loaded serial 42 Jun 30 12:23:07 host named[22626]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 Jun 30 12:23:07 host named[22626]: zone 255.in-addr.arpa/IN: loaded serial 42 Jun 30 12:23:07 host named[22626]: 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 Jun 30 12:23:07 host named[22626]: zone orgenen.com/IN: loaded serial 2005063002 Jun 30 12:23:07 host named[22626]: zone localdomain/IN: loaded serial 42 Jun 30 12:23:07 host named[22626]: zone localhost/IN: loaded serial 42 Jun 30 12:23:07 host named[22626]: zone ns1.orgenen.net/IN: could not find NS and/or SOA records Jun 30 12:23:07 host named[22626]: zone ns1.orgenen.net/IN: has 0 SOA records Jun 30 12:23:07 host named[22626]: zone ns1.orgenen.net/IN: has no NS records Jun 30 12:23:07 host named[22626]: zone ns2.orgenen.net/IN: could not find NS and/or SOA records Jun 30 12:23:07 host named[22626]: zone ns2.orgenen.net/IN: has 0 SOA records Jun 30 12:23:07 host named[22626]: zone ns2.orgenen.net/IN: has no NS records Jun 30 12:23:07 host named[22626]: running Jun 30 12:23:07 host named[22626]: zone orgenen.com/IN: sending notifies (serial 2005063002)





    • The server hostname is set to host.orgenen.com
      I have created an account orgenen.com
      Access to server via IP works fine.
      I have child nameservers setup for the orgnen.net at my domain providor. In the last 2 hours I request for reverse dns for my server.
      I have specified that orgenen.com use the name servers ns1/ns2.orgenen.net

    Any ideas? Need anymore information?
    Note: ping orgenen.com gives the error unknown host.
     
  2. gpreston

    gpreston Well-Known Member

    Joined:
    Jan 31, 2004
    Messages:
    61
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    West Chester, PA
    While on the box, can you do a 'dig' on all the domain names and verify that your DNS server is responding properly?

    Also, can you do a dig from a different linux box somewhere else and tell it to query against the IP of your box? Make sure that it is able to answer to remote boxes?
     
  3. jhair

    jhair Registered

    Joined:
    Mar 22, 2005
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Oh yeah so stupid

    Yeah well after following all the instructions out there. There are some really good resources out there.

    The final problem at the end of it all was that the firewall was blocking port 53 tcp/udp. Yes rookie mistake number 1.

    Thanks for your help, regardless of my mistake.

    :eek: :eek: :eek:
     
  4. gpreston

    gpreston Well-Known Member

    Joined:
    Jan 31, 2004
    Messages:
    61
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    West Chester, PA
    Hehe, it happens. Its why I asked you to make sure you could do a query from a remote host and get an answer =P Glad its fixed now.
     
Loading...

Share This Page