|
|
 |  |
Re: Setting Up Reverse DNS QueryFrom: Men & Mice Support Date: Thursday, November 11, 2004
Time: 9:37:42 amAt 5:11 PM +0000 11/11/04, Stuart Douglas wrote:
>Subject: Re: Setting Up Reverse DNS Query
>From: "Men & Mice Support" <cbuxton@menandmice.com>
>Date: Tue, 9 Nov 2004 13:54:17 -0800
>
>At 3:28 PM +0000 11/9/04, Stuart Douglas wrote:
>>From: "Men & Mice Support" <cbuxton@menandmice.com>
>>Date: Mon, 8 Nov 2004 09:46:00 -0800
>>
>>>>Creative, and perfectly legal. You don't even need to separate these
>>>>into a reverse zone if you don't want to - just create records like
>>>>this for each of your IP addresses:
>>
>>>>82.233.20.212.in-addr.groovychocolate.com. PTR mail.groovychocolate.com.
>>
>>>Ah, I was doing fine until this point Chris - our mail server and
>>>Quick DNS are both on the 82 box, so I've already got a record :
>>
>>>82.233.20.212.in-addr.groovychocolate.com. PTR ns.groovychocolate.com
>>
>>>Is it allowable to have both records, ie:
>>
>>>82.233.20.212.in-addr.groovychocolate.com. PTR mail.groovychocolate.com
>>>82.233.20.212.in-addr.groovychocolate.com. PTR ns.groovychocolate.com
>
>>It's not against the rules, but it's a bad idea in this case. You
>>should have just the one pointing to mail.groovychocolate.com.
>
>But won't that mean that my nameserver won't resolve? Or am I
>barking up the wrong tree altogether?
You've misunderstood the purpose of PTR records.
For the most part, PTR records are strictly for convenience. However,
some security mechanisms, such as spam blocking, rely on them.
Therefore, you should always try to have exactly one PTR record for
any machine whose name is important (such as a mail server), and at
least one for any client machine. It's often best, in fact, to have
exactly one for each IP address in use.
Chris Buxton
Men & Mice - Making DNS Easy
Customer Service and Sales Engineer
|

Return to Digital Point Solutions' Home Page |