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.

Name server and Hostname problem

Discussion in 'General Discussion' started by don_will, Aug 22, 2007.

  1. don_will

    don_will Well-Known Member

    Joined:
    Jun 26, 2007
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Cpanel
    hello,

    my NS and hostname cannt resolve. but another hosting account can resolve. before ive changed named.conf name server can resolve. ive change named.conf reading this post.

    http://forums.cpanel.net/showthread.php?t=69447&highlight=DNS+problem

    after that. NS and hostname cannt resolve. i dont understand now. here is my named.conf original. :

    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 :
    
            zone "ns3.fartuah.net" {
                    type master;
                    file "/var/named/ns3.fartuah.net.db";
            };
    
            zone "ns4.fartuah.net" {
                    type master;
                    file "/var/named/ns4.fartuah.net.db";
            };
    
            zone "mercury.fartuah.net" {
                    type master;
                    file "/var/named/mercury.fartuah.net.db";
            };
    
     zone "funwindow.net" {
                    type master;
                    file "/var/named/funwindow.net.db";
            };
    
            zone "irc.funwindow.net" {
                    type master;
                    file "/var/named/irc.funwindow.net.db";
            };
    };
    
    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 "ns3.fartuah.net" {
                            type master;
                            file "/var/named/ns3.fartuah.net.db";
                    };
    
                    zone "ns4.fartuah.net" {
                            type master;
                            file "/var/named/ns4.fartuah.net.db";
    };
    
                    zone "mercury.fartuah.net" {
                            type master;
                            file "/var/named/mercury.fartuah.net.db";
                    };
    
                    zone "fartuah.net" {
                            type master;
                            file "/var/named/fartuah.net.db";
                    };
    
    
                    zone "funwindow.net" {
                            type master;
                            file "/var/named/funwindow.net.db";
                    };
    
                    zone "irc.funwindow.net" {
                            type master;
                            file "/var/named/irc.funwindow.net.db";
                    };
    };
    
    and this is after modified.

    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;
    recursion no;
    
    // 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.
    
    /* 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:
    */
    // you'd probably want to deny recursion to external clients, so you don't
    // end up providing free DNS service to all takers
    // 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 "ns3.fartuah.net" {
                            type master;
                            file "/var/named/ns3.fartuah.net.db";
                    };
    
                    zone "ns4.fartuah.net" {
                            type master;
                            file "/var/named/ns4.fartuah.net.db";
                    };
    
                    zone "mercury.fartuah.net" {
                            type master;
                            file "/var/named/mercury.fartuah.net.db";
                    };
    
                    zone "fartuah.net" {
                            type master;
                            file "/var/named/fartuah.net.db";
                    };
    
    
                    zone "funwindow.net" {
                            type master;
                            file "/var/named/funwindow.net.db";
                    };
    
                    zone "irc.funwindow.net" {
                            type master;
                            file "/var/named/irc.funwindow.net.db";
                    };
    im using WHM 11.2.0 cPanel 11.10.0-R16448
    CENTOS Enterprise 5 i686
     
    #1 don_will, Aug 22, 2007
    Last edited: Aug 22, 2007
  2. don_will

    don_will Well-Known Member

    Joined:
    Jun 26, 2007
    Messages:
    62
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Cpanel
    sorry. probs Solved.
     
Loading...

Share This Page