Reverse DNS

[Jerry Feldman]

I've been fighting the reverse DNS battle for months for blu.org. The 
problem was that I was never able to communicate to NDEV (who owns the IP 
address block) exactly what I wanted. Eventually, I asked them to create a 
PTR record. 
But we did set up a zone on our internal DNS server. We have 5 IP addresses 
assigned, but in all actuality we only use 231. 
$TTL 3600
@       IN      SOA     asgard.blu.org. root.blu.org. (
                        2002081100  ; serial
                        28800 ; refresh
                        1800 ; retry
                        604800 ; expire
                        3600 ; ttk
                        )

        IN      NS      msb.significant.com.
        IN      NS      ns.blu.org.
        IN      NS      ns1.usdatacenters.com.
        IN      NS      ns2.usdatacenters.com.
        IN      NS      ns3.usdatacenters.com.
        IN      NS      ns4.usdatacenters.com.


230     IN      PTR     tarnhelm.blu.org.
231     IN      PTR     asgard.blu.org.
232     IN      PTR     vhcma.blu.org.
233     IN      PTR     heli-vets.blu.org.
234     IN      PTR     macwoburn.blu.org.

On 15 Aug 2002 at 11:54, Brenda A. Bell wrote:

> Can someone point me to a good resource for getting a better
> understanding of reverse DNS and the role it plays in the big picture?

-- 
Jerry Feldman <gaf at blu.org>
Associate Director
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9