From: Douglas M. Long
Sent: Thu 6/3/2004 12:07 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] PTR records - why?
Reverse lookups are sometimes performed in an attempt to minimize spoofing
also. Reverse lookup can be very useful and/or necessary.
-----Original Message-----
From: Steve Rochford [mailto:[EMAIL PROTECTED]]On
Behalf Of Steve Rochford
Sent: Thursday, June 03, 2004 3:08 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] PTR records - why?
If you ever need to connect to a Unix machine then it will try to do a
reverse look up which needs the Ptr records.
Steve
-----Original Message-----
From: "Rutherford, Robert" <[EMAIL PROTECTED]>
Sent: 01/06/04 09:50:48
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Subject: RE: [ActiveDir] PTR records - why?
You don't specifically need pointers...as far as I can remember it is
just good practice.
I do find it useful from an admin persepctive at times, i.e. resolving
an IP back to an IP in a troubleshooting scenario (at times).
You aren't going to lose anything by creating them.
Rob
-----Original Message-----
From: Jan Wilson [mailto:[EMAIL PROTECTED]]
Sent: 30 May 2004 02:22
To: [EMAIL PROTECTED]
Subject: [ActiveDir] PTR records - why?
We have a Windows 2000 forest with multiple child domains. No web
servers. No remote hosted mail servers. No external access. (That I know
about at least!) Our DNS is integrated to active directory. Fellow
administrators are adamant we should create reverse lookup zones for all
our subnets. This would assist name resolution for our NT4 workstations
they claim. Stuff and nonsense I claim. Is there any reason to use PTR
records on an AD domain?
Thanks!
