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 problems! Lame nameservers, sites not working!

Discussion in 'Bind / DNS / Nameserver Issues' started by Fid, Jun 16, 2007.

  1. Fid

    Fid Member

    Joined:
    Dec 1, 2004
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Hi all,

    cPanel/WHM server... and no sites are working due to the nameservers I believe.

    On a DNSStuff check; http://www.dnsstuff.com/tools/dnsreport.ch?&domain=www.my150mb.com; it reports lame nameservers (among other stuff).

    The nameservers have been registered with the domain, at godaddy.com.

    I'm led to believe it is something on the server... that is blocking queries or something.

    At first I thought it was apf, but I turned that off and tried again, no luck.

    Currently, my named.conf is;

    include "/etc/rndc.key";

    controls {
    inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
    };

    options
    {
    /* make named use port 53 for the source of all queries, to allow
    * firewalls to block all ports except 53:
    */
    query-source port 53;

    // Put files that named is allowed to write in the data/ directory:
    directory "/var/named"; // the default
    dump-file "data/cache_dump.db";
    statistics-file "data/named_stats.txt";
    memstatistics-file "data/named_mem_stats.txt";
    allow-recursion { localhost; };
    };

    logging
    {
    /* If you want to enable debugging, eg. using the 'rndc trace' command,
    * named will try to write the 'named.run' file in the $directory (/var/named).
    * By default, SELinux policy does not allow named to modify the /var/named directory,
    * so put the default debug log file in data/ :
    */
    channel default_debug {
    file "data/named.run";
    severity dynamic;
    };
    };

    // All BIND 9 zones are in a "view", which allow different zones to be served
    // to different types of client addresses, and for options to be set for groups
    // of zones.
    //
    // By default, if named.conf contains no "view" clauses, all zones are in the
    // "default" view, which matches all clients.
    //
    // If named.conf contains any "view" clause, then all zones MUST be in a view;
    // so it is recommended to start off using views to avoid having to restructure
    // your configuration files in the future.

    view "localhost_resolver"
    {
    /* This view sets up named to be a localhost resolver ( caching only nameserver ).
    * If all you want is a caching-only nameserver, then you need only define this view:
    */
    match-clients { localhost; };
    match-destinations { localhost; };
    recursion yes;

    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };

    /* these are zones that contain definitions for all the localhost
    * names and addresses, as recommended in RFC1912 - these names should
    * ONLY be served to localhost clients:
    */
    include "/var/named/named.rfc1912.zones";
    };

    view "internal"
    {
    /* This view will contain zones you want to serve only to "internal" clients
    that connect via your directly attached LAN interfaces - "localnets" .
    */
    match-clients { localnets; };
    match-destinations { localnets; };
    recursion yes;

    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };

    // include "/var/named/named.rfc1912.zones";
    // you should not serve your rfc1912 names to non-localhost clients.

    // These are your "authoritative" internal zones, and would probably
    // also be included in the "localhost_resolver" view above :
    };

    view "external"
    {
    /* This view will contain zones you want to serve only to "external" clients
    * that have addresses that are not on your directly attached LAN interface subnets:
    */
    match-clients { !localnets; !localhost; };
    match-destinations { !localnets; !localhost; };

    recursion no;
    // you'd probably want to deny recursion to external clients, so you don't
    // end up providing free DNS service to all takers

    // all views must contain the root hints zone:
    zone "." IN {
    type hint;
    file "/var/named/named.ca";
    };

    // These are your "authoritative" external zones, and would probably
    // contain entries for just your web and mail servers:

    // BEGIN external zone entries

    zone "my150mb.com" {
    type master;
    file "/var/named/my150mb.com.db";
    };
    };

    ... nothing unusual is there?

    Any help would be appreciated!!
     
  2. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Is "named" actually running?
    Code:
    service named restart
    Is there a DNS entry for your name servers?
     
  3. Fid

    Fid Member

    Joined:
    Dec 1, 2004
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Hi mate,

    Yes, named is running.

    As for the DNS entry for my nameservers, I'm guessing you mean on the actual server?

    If so, yes on the DNS zone there are NS records (2) and A records for them both.

    At godaddy, they are listed under "Host Settings" with both ns1 and ns2 and the two ip's.

    Another error check says;

    Tried to fetch SOA record for domain, but DNS server ns1.my150mb.com [66.79.171.108] returned error code Refused
    Tried to fetch SOA record for domain, but DNS server ns2.my150mb.com [66.79.191.217] returned error code Refused
    0 server(s) are alive

    It goes on to say... CheckDNS received an answer to the query, but the answer indicates the error code mentioned. This means that remote DNS is ONLINE, but cannot give the answer for some reason.

    Therefore, I'm guessing this IS server related?

    Thanks!
     
  4. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Yep, am sure the problem is at your server. I take it these IPs 66.79.171.108 and 66.79.191.217 belong to your server, yes? and your DNS zone lists them as your name servers for my150mb.com ??
     
  5. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Try also running # /scripts/fixnamed and /scripts/fixrndc
     
  6. Fid

    Fid Member

    Joined:
    Dec 1, 2004
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Hi,

    Yes they belong to the server (3 on there in total). - Checking on the second one though (just in case!)

    And yes, they are listed in the DNS zone.

    Just ran the two commands now, seeing if that works. Never knew DNS could be so confusing heh
     
    #6 Fid, Jun 16, 2007
    Last edited: Jun 16, 2007
Loading...

Share This Page