mike_steele_2000 at yahoo.com
Thu Jul 12 22:32:20 MSD 2007
In response to
Users are caught in the middle of a debate over whether reverse records
should be used for identification. The pro argument is that it helps
identify spammers and abusers. The con argument (which I believe) is
that the purpose of domain names is convenience: so you don't have to
remember a number, and so that a site can maintain a "permanent"
identifier even if they move to another server or a different ISP. You
shouldn't /have/ to have a domain name, much less have it set to any
particular value. And to identify scRipT kIddyZ, just do a simple
traceroute. The second-last hop is their ISP (or part of their own
network), and ISPs always have their own domain name showing. And what
if a computer has several domain names, each hosted at a different
organization? There can be only one reverse record, so all the other
names will be left out in the cold.
I always assumed the cost to be for the liability. Otherwise they would
just automate it and have you do it online. This seems to thwart spam;
email administrators put an additional reverse record lookup to make
sure it is not a "rogue" mail server put online by just anyone. They
have to contact their ISP and get a reverse record. It's like adding
locks to your door. It isn't a guarantee - just a deterrent. That one
reverse record is for the mail server. Otherwise RR's are not necessary
and so it doesn't matter if there are multiple domains. You can CNAME
the domains MX records to the actual server name.
Dunno for sure but thats my 2 cents.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the TAG