 |  |
one case where you need it is if you intend to install software that
Re: Quickdns-Talk Digest #1012 - 15/09/01
From: andrew kagan
Date: Sunday, September 16, 2001
Time: 9:13:52 am
evaluates whether or not the computer being installed on is in the U.S.,
such as a M$oft browser with "strong encryption"...M$oft won't let you
download it unless the PTR record for that IP address resolves to a U.S.
domain.
----- Original Message -----
From: "Dave Cooper" <dcooper@acton.org>
To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
Sent: Sunday, September 16, 2001 11:56 AM
Subject: Re: Quickdns-Talk Digest #1012 - 15/09/01
> So the average workstation doesn't really need to have a PTR record setup
> for it?
>
> Dave
> >
> > Subject: Re: PTR records
> > From: "Global Homes Webmaster" <webmaster@globalhomes.com>
> > Date: Fri, 14 Sep 2001 13:33:42 -0700
> >
> > On 09/14/01 at 16:18, Dave Cooper wrote:
> >
> >> hi,
> >>
> >> I've been told that having a reverse lookup for each IP on my network
is a
> >> good thing. My question is: What would this look like in the reverse
> >> domain? Can I do a range of IP #'s on a single line, or do I have to
do an
> >> individual line for each number?
> >
> > First, you need to have your ISP delegate the reverse zone to your name
> > servers. Once that's done you need a separate PTR record in the reverse
zone
> > for each IP number that has a host name. E.g.:
> >
> > z.y.x.in-addr.arpa. NS ns1.your.domain.
> > z.y.x.in-addr.arpa. NS ns2.your.domain.
> > 1.z.y.x.in-addr.arpa. PTR host1.your.domain.
> > 2.z.y.x.in-addr.arpa. PTR host2.your.domain.
> > 3.z.y.x.in-addr.arpa. PTR host3.your.domain.
> > etc.
> >
> > Christopher Bort | cbort@globalhomes.com
> > Webmaster, Global Homes | webmaster@globalhomes.com
> > <http://www.globalhomes.com/> | PGP public key available on request
> >
> > ----------------------------------------------------------------------
> > End of Quickdns-Talk Digest
> >
> >
>
>
>
Messages In This Thread:
Return to Digital Point Solutions' Home Page