rDNS - Setting up a reverse DNS

Discussion in 'Mail Server' started by Lamer, Mar 4, 2013.

  1. Lamer

    Lamer New Member

    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    Hi all,

    I've just finished setting up a new CentOs 6.2 VPS server. NS + email has been setup and Glue records created

    I can't seem to setup the rDNS though. Is this setup on the server or by the domain manager?


    intodns.com message

    Code:
    Reverse MX A records (PTR)
    
    ERROR: No reverse DNS (PTR) entries. The problem MX records are: 
    195.86.50.27.in-addr.arpa -> no reverse (PTR) detected
     You should contact your ISP and ask him to add a PTR record for your ips 
    

    /etc/named.conf

    Code:
    options {
            empty-zones-enable no;
    //      listen-on port 53 { 127.0.0.1; };
    //      listen-on-v6 port 53 { ::1; };
            directory       "/var/named";
            dump-file       "/var/named/data/cache_dump.db";
            statistics-file "/var/named/data/named_stats.txt";
            memstatistics-file "/var/named/data/named_mem_stats.txt";
    //      allow-query     { localhost; };
            recursion yes;
    
    //      dnssec-enable yes;
    //      dnssec-validation yes;
    //      dnssec-lookaside auto;
    
            /* Path to ISC DLV key */
            bindkeys-file "/etc/named.iscdlv.key";
    
            managed-keys-directory "/var/named/dynamic";
    };
    
    logging {
            channel default_debug {
                    file "data/named.run";
                    severity dynamic;
            };
    };
    
    zone "." IN {
            type hint;
            file "named.ca";
    };
    
    include "/etc/named.rfc1912.zones";
    include "/etc/named.root.key";
    
    zone "example.com" {
            type master;
            file "/var/named/example.com.hosts";
            };
    zone "195.86.50.27.in-addr.arpa" {
            type master;
            file "/var/named/27.50.86.195.rev";
            };
    zone "86.50.27.in-addr.arpa" {
            type master;
            file "/var/named/27.50.86.rev";
            };
    

    zone example.com

    Code:
    $ttl 38400
    example.com.                  IN      SOA     ns1.example.com. webmaster.example.com. (
                                    1361472182
                                    10800
                                    3600
                                    604800
                                    38400 )
    example.com.                  IN      A       27.50.86.195
    www                             IN      A       27.50.86.195
    mail                            IN      A       27.50.86.195
    ftp                             IN      A       27.50.86.195
    ns1                             IN      A       27.50.86.195
    ns2                             IN      A       27.50.86.195
    example.com.                  IN      NS      ns1.example.com.
    example.com.                  IN      NS      ns2.example.com.
    example.com.                  IN      MX      10 mail.example.com.
    

    zone 195.86.50.27.in-addr.arpa


    Code:
    $ttl 38400
    195.86.50.27.in-addr.arpa.      IN      SOA     ns1.example.com. webmaster.example.com. (
                            1361687161
                            10800
                            3600
                            604800
                            38400 )
    195.86.50.27.in-addr.arpa.      IN      NS      ns1.example.com.
    195.86.50.27.in-addr.arpa.      PTR     example.com.
    

    zone 86.50.27.in-addr.arpa

    Code:
    $ttl 38400
    86.50.27.in-addr.arpa.  IN      SOA     ns1.example.com. webmaster.example.com. (
                            1361687161
                            10800
                            3600
                            604800
                            38400 )
    86.50.27.in-addr.arpa.  IN      NS      ns1.example.com.
    86.50.27.in-addr.arpa.  PTR     example.com.
    
  2. nixsavy

    nixsavy Member

    Messages:
    65
    Likes Received:
    17
    Trophy Points:
    8
    rDNS perform a reverse lookup, with this record, DNS can determine the fully qualified domain name associated with an IP address. In Name field add last octet of server’s IP address, in class field IN and in Type field PTR and in Data field Fully qualified Domain name or hostname as below:

    27 PTR example.com.

    Restart named and check as below if it is setup properly.
    Code:
    host serverIP

Share This Page