Results 1 to 1 of 1

Thread: Resolve DNS issues on cpanel 11.x Beta

  1. #1
    Jordan is offline Newbie Net Builder
    Join Date
    Dec 2008
    Posts
    59
    Blog Entries
    1
    Thanks
    83
    Thanked 8 Times in 5 Posts

    Resolve DNS issues on cpanel 11.x Beta

    Hello,

    I have come accross an issue with DNS in cpanel 11.x , where named.conf is badly configured by cpanel ,

    Here is how a DNS report from dnsstuff.com would look because of this :

    FAILS for SOA record
    Fails for lame nameservers .

    Here's how to fix it ,

    SSH to server ,

    Backup your named.conf file by

    cp /etc/named.conf named.conf.back

    then
    pico /etc/named.conf

    Replace
    HTML Code:
    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";
    };
    
    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
    With
    HTML Code:
    include "/etc/rndc.key";
    
    controls {
            inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
    };
    And then goto bottom of the file and remove

    }; at the bottom .

    Save file and exit

    then test config
    service named configtest
    if you have done this correctly , it should display something like this:

    zone blue.xxx.com/IN: loaded serial 2007070901
    zone xxx.com/IN: loaded serial 2007070906
    zone ns1.xxx.com/IN: loaded serial 2007070901
    zone server.xxx.com/IN: loaded serial 2007071001
    zone xxx.net/IN: loaded serial 2007071001

    Then restart named by

    service named restart

    Thats it! , your DNS should be working now .

  2. Thanked by:

    Will.Spencer (16 February, 2009)

Similar Threads

  1. Replies: 0
    Last Post: 8 June, 2010, 19:57 PM
  2. CSS issues
    By 1901gt in forum Programming
    Replies: 4
    Last Post: 24 September, 2009, 06:56 AM
  3. Wordpress 2.8.x SERIOUS Memory Issues
    By Shenron in forum Wordpress
    Replies: 7
    Last Post: 16 September, 2009, 13:42 PM
  4. SEO Issues?
    By Electron in forum Promoting
    Replies: 4
    Last Post: 29 July, 2009, 11:01 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •