<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">You can point PTR records anywhere you
want. In fact, there's nothing that even says that PTR records are
limited to representing reverse mappings, or that they can only
appear in the in-addr.arpa hierarchy. Strictly speaking, they're
just name-to-name mappings, _sans_ the special "aliasing" function
of CNAMEs and consequent referential restrictions, like the
infamous "CNAME and other" rule. I wish more people would
understand that for simple name-to-name mapping functions, PTR
records are *superior* to TXT records, since PTRs benefit from
label compression, while TXT records do not. If one wants to
encode more information in the RDATA than just a name, however,
then one requires the extra "freedom" of TXT records.<br>
<br>
- Kevin<br>
On 4/17/2013 10:49 AM, PAVLOV Misha wrote:<br>
</div>
<blockquote
cite="mid:281902A29B6FA54CA70201CCF36103490AE4BFBB93@MBXNYC601.hermes.si.socgen"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Folks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Wonder if someone can kindly confirm that
there is nothing
wrong with having a PTR record in one of the subnet zone file
(we are authorative
for) with PTR to the name owned by another office (domain). A
server exchange.north.our.company
(owned and registered in north.our.company domain) installed
here, on the same
network as all local south.our.company machines. We own, are
authorative and
maintain the db.1.2.3 subnet reverse zone, but not the
north.our.company name registered
far away.<o:p></o:p></p>
<p class="MsoNormal">
<o:p></o:p></p>
<p class="MsoNormal">The DNS server is running BIND 9.3.4-P1 <o:p></o:p></p>
<p class="MsoNormal">The routine DNS updates are done via the
GUI (phpMyAdmin
derivative) which has no provision for adding PTR records only
and the team in
charge is hesitant to manually add the<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">11 IN PTR
exchange.north.our.company.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To the db.1.2.3 zone, populated with
consistent entries like
<o:p></o:p></p>
<p class="MsoNormal">. . . <o:p></o:p></p>
<p class="MsoNormal">12 IN PTR
robocop.south.our.company.<o:p></o:p></p>
<p class="MsoNormal">13 IN PTR
terminator.south.our.company.<o:p></o:p></p>
<p class="MsoNormal">14 IN PTR
diehard.south.our.company.<o:p></o:p></p>
<p class="MsoNormal">. . .<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">TIA<o:p></o:p></p>
</div>
<p>*************************************************************************
<br>
This message and any attachments (the "message") are
confidential, intended <br>
solely for the addressee(s), and may contain legally privileged
information. <br>
Any unauthorised use or dissemination is prohibited. E-mails are
susceptible <br>
to alteration. Neither SOCIETE GENERALE nor any of its
subsidiaries or <br>
affiliates shall be liable for the message if altered, changed
or falsified.<br>
Please visit <a class="moz-txt-link-freetext" href="http://swapdisclosure.sgcib.com">http://swapdisclosure.sgcib.com</a> for important
information with<br>
respect to derivative products.<br>
*************************************************************************</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Please visit <a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list
bind-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a></pre>
</blockquote>
<br>
</body>
</html>