<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
thanks for your comment.<br><br>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.<br>IF no reverse, it can be blacklisted for some reasons or having some problems with services asking a reverse dns resolution.<br><br><br><div><div id="SkyDrivePlaceholder"></div>> From: spainj@countryday.net<br>> To: hugobxl@hotmail.com<br>> CC: bind-users@lists.isc.org<br>> Subject: RE: reverse dns for IPV6 ranges<br>> Date: Mon, 5 Mar 2012 21:15:53 +0000<br>> <br>> > Can anyone help me with its experience on reverse dns for IPV6?<br>> > Presently, when we reverse an IPV4 subnet for clients, we configure all the reverse for the whole subnet.<br>> > It is a lot of PTR's but perfectly manageable.<br>> > With IPV6, the number of IP's that we will receive is amazing....<br>> > So...it seems impossible for every single IPV6 inthe range to configure a PTR.<br>> > So...what to do?<br>> > What is the common practice?<br>> > What is possible with BIND?<br>> <br>> 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:<br>> <br>> $ORIGIN .<br>> $TTL 3600 ; 1 hour<br>> a.c.0.2.0.7.8.4.1.0.0.2.ip6.arpa IN SOA ns1.countryday.net. hostmaster.countryday.net. (<br>> 2012030101 ; serial<br>> 86400 ; refresh (1 day)<br>> 3600 ; retry (1 hour)<br>> 1209600 ; expire (2 weeks)<br>> 3600 ; minimum (1 hour)<br>> )<br>> NS ns1.countryday.net.<br>> NS ns2.countryday.net.<br>> $ORIGIN 9.0.0.0.a.c.0.2.0.7.8.4.1.0.0.2.ip6.arpa.<br>> a.5.6.9.f.9.e.4.3.4.3.e.f.a.0.8 PTR ns2.countryday.net.<br>> $ORIGIN 8.5.1.0.a.c.0.2.0.7.8.4.1.0.0.2.ip6.arpa.<br>> 2.9.1.f.1.d.2.1.b.f.7.5.7.f.8.0 PTR ns1.countryday.net.<br>> <br>> I would also be interested in hearing about the practices of others. Jeff.<br>> <br>> Jeffry A. Spain<br>> Network Administrator<br>> Cincinnati Country Day School<br>> <br></div> </div></body>
</html>