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.

reverse DNS not working

Discussion in 'Bind / DNS / Nameserver Issues' started by pisdoktor, May 5, 2012.

  1. pisdoktor

    pisdoktor Registered

    Joined:
    May 5, 2012
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hi,

    First of all, sorry for my bad english. I have a problem with rDNS. Server Main ip address is 88.255.103.220

    /etc/resolv.conf:
    Code:
    search afyonhsm.gov.tr
    domain afyonhsm.gov.tr
    nameserver 208.67.222.222
    nameserver 208.67.220.220
    /etc/hosts:
    Code:
    88.255.103.220	afyonhsm.gov.tr afyonhsm
    127.0.0.1		localhost
    192.168.20.5		halk.afyonhsm.gov.tr halk
    how can i create rDNS? Which files to be edited? Please help me!
     
  2. pisdoktor

    pisdoktor Registered

    Joined:
    May 5, 2012
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    I create a file like this link:Configuring Reverse DNS in WHM but not working.

    /var/named/103.255.88.in-addr.arpa.db:
    Code:
    
    ; cPanel first:11.32.2.25 (update_time):1336247484 Cpanel::ZoneFile::VERSION:1.3 hostname:halk.afyonhsm.gov.tr latest:11.32.2.25
    ; Zone file for 103.255.88.in-addr.arpa
    $TTL 14400
    103.255.88.in-addr.arpa.	86400	IN	SOA	ns1.afyonhsm.gov.tr.	webmaster.afyonhsm.gov.tr.	(
    						2012050502 ;Serial Number
    						86400 ;refresh
    						7200 ;retry
    						3600000 ;expire
    						86400 ;minimum
    	)
    103.255.88.in-addr.arpa.	86400	IN	NS	ns1.afyonhsm.gov.tr.
    103.255.88.in-addr.arpa.	86400	IN	NS	ns2.afyonhsm.gov.tr.
    103	14400	IN	PTR	afyonhsm.gov.tr.
    104	14400	IN	PTR	mail.afyonhsm.gov.tr.
    105	14400	IN	PTR	secure.afyonhsm.gov.tr.
    /etc/named.conf:
    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;
    
        /* We no longer enable this by default as the dns posion exploit
            has forced many providers to open up their firewalls a bit */
    
        // Put files that named is allowed to write in the data/ directory:
        directory                "/var/named"; // the default
        pid-file                 "/var/run/named/named.pid";
        dump-file                "data/cache_dump.db";
        statistics-file          "data/named_stats.txt";
       /* memstatistics-file     "data/named_mem_stats.txt"; */
        allow-transfer {"none";};
    };
    
    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         { 127.0.0.1/24; };
        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;
    
        // 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 "afyonhsm.gov.tr" {
    	type master;
    	file "/var/named/afyonhsm.gov.tr.db";
    
    };
    
    zone "afyonhalksagligi.gov.tr" {
    	type master;
    	file "/var/named/afyonhalksagligi.gov.tr.db";
    };
    
    
    zone "103.255.88.in-addr.arpa" {
    	type master;
    	file "/var/named/103.255.88.in-addr.arpa.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:
     */
        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:
    
        // These are your "authoritative" external zones, and would probably
        // contain entries for just your web and mail servers:
    
        // BEGIN external zone entries
    
    zone "afyonhsm.gov.tr" {
    	type master;
    	file "/var/named/afyonhsm.gov.tr.db";
    };
    
    zone "afyonhalksagligi.gov.tr" {
    	type master;
    	file "/var/named/afyonhalksagligi.gov.tr.db";
    };
    
    
    zone "103.255.88.in-addr.arpa" {
    	type master;
    	file "/var/named/103.255.88.in-addr.arpa.db";
    };
    
    };
     
Loading...

Share This Page