<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: PTR zone / VLSM issue</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText56578 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>I agree, it's
arbitrary. If you are wanting to format the name of your zone similarly to
the RFC, I believe the format would be 96/27.51.212.195.in-addr.arpa (for the
subnet 195.212.51.96/27).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> bind-users-bounces@lists.isc.org on behalf
of Alan Clegg<BR><B>Sent:</B> Sun 3/15/2009 4:55 PM<BR><B>To:</B>
bind-users@lists.isc.org<BR><B>Subject:</B> Re: PTR zone / VLSM
issue<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Charles Lee wrote:<BR><BR>> I believe its format should
be: 96-127.51.212.195.in-addr.arpa<BR>><BR>> The problem I seem to
be having is what order the 96-127 should be in,<BR>> because in normal
format the network is 195.212.51.96-127 (we basically<BR>> run address .96 to
address .127)<BR>><BR>> Can anyone help out with the proper format of the
zone and what a PTR<BR>> record would look like?<BR><BR>It matters not a bit
nor a twiddle, as it is just a label that needs to<BR>be "pointed to" by the
actual in-addr label
elsewhere.<BR><BR>96.fred.51.212.195.in-addr.arpa.
IN PTR mymachine.foo.com.<BR><BR>would work fine as long as you
had:<BR><BR>fred.51.212.195.in-addr.arpa. IN NS
delegated.foo.com.<BR>96.51.212.195.in-addr.arpa. IN CNAME
96.fred.51.212.195.in-addr.arpa.<BR><BR>on the nameserver that was actually
delegated 51.212.195.in-addr.arpa.<BR><BR>(feel free to use $GENERATE to create
the above CNAMEs)<BR><BR>AlanC<BR><BR></FONT></P></DIV>
</BODY>
</HTML>