reverse dns for IPV6 ranges

[hugo hugoo]

thanks for your comment.

But if only some IP have e reverse..what about the other server who have received an IP in the range? Ip that can be changed every x hours.
IF no reverse, it can be blacklisted for some reasons or having some problems with services asking a reverse dns resolution.


> From: spainj at countryday.net
> To: hugobxl at hotmail.com
> CC: bind-users at lists.isc.org
> Subject: RE: reverse dns for IPV6 ranges
> Date: Mon, 5 Mar 2012 21:15:53 +0000
> 
> > Can anyone help me with  its experience on reverse dns for IPV6?
> > Presently, when we reverse an IPV4 subnet for clients, we configure all the reverse for the whole subnet.
> > It is a lot of PTR's but perfectly manageable.
> > With IPV6,  the number of IP's that we will receive is amazing....
> > So...it seems impossible for every single IPV6 inthe range to configure a PTR.
> > So...what to do?
> > What is the common practice?
> > What is possible with BIND?
> 
> For our IPv6 address space 2001:4870:20ca::/48, I created a reverse lookup zone a.c.0.2.0.7.8.4.1.0.0.2.ip6.arpa and arranged for delegation from our ISP.  I included PTR records only for those hosts accessible from the outside. Internal DNS is Windows Active Directory integrated. Here's a sample from the zone file, which contains about 25 PTR records in all:
> 
> $ORIGIN .
> $TTL 3600       ; 1 hour
> a.c.0.2.0.7.8.4.1.0.0.2.ip6.arpa IN SOA ns1.countryday.net. hostmaster.countryday.net. (
>                                 2012030101 ; serial
>                                 86400      ; refresh (1 day)
>                                 3600       ; retry (1 hour)
>                                 1209600    ; expire (2 weeks)
>                                 3600       ; minimum (1 hour)
>                                 )
>                         NS      ns1.countryday.net.
>                         NS      ns2.countryday.net.
> $ORIGIN 9.0.0.0.a.c.0.2.0.7.8.4.1.0.0.2.ip6.arpa.
> a.5.6.9.f.9.e.4.3.4.3.e.f.a.0.8 PTR ns2.countryday.net.
> $ORIGIN 8.5.1.0.a.c.0.2.0.7.8.4.1.0.0.2.ip6.arpa.
> 2.9.1.f.1.d.2.1.b.f.7.5.7.f.8.0 PTR ns1.countryday.net.
> 
> I would also be interested in hearing about the practices of others. Jeff.
> 
> Jeffry A. Spain
> Network Administrator
> Cincinnati Country Day School
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20120305/2d1920b1/attachment.html>