<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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]-->
</head>
<body>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I was told by a Cisco engineer that cisco-internal is no longer supported and it didn’t work for us after we enabled MRA. I think the pinpoint subdomain being
referred to now is creating the _<i>cisco-uds.</i>_tcp SRV record as a domain on your internal DNS server. That works perfectly.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cisco-voip [mailto:cisco-voip-bounces@puck.nether.net]
<b>On Behalf Of </b>Erick Wellnitz<br>
<b>Sent:</b> 10 April 2015 8:32 AM<br>
<b>To:</b> Anthony Holloway<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] jabber dual domain question<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I'm seeing the 10.6.2 client query for _cisco-uds._<a href="http://tcp.xyz.com">tcp.xyz.com</a>,
_cuplogin._tcp.xyz.com...then _collab-edge._<a href="http://tls.xyz.com">tls.xyz.com</a><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don't see a query for <a href="http://cisco-internal.xyz.com">
cisco-internal.xyz.com</a><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Apr 10, 2015 at 8:09 AM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">According to the document you linked, Jabber will first perform this query:<br>
<br>
_cisco-uds._<a target="_blank" href="http://tcp.xyz.com">tcp.xyz.com</a><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If nothing comes back, then it will try:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">_cisco-uds._<a target="_blank" href="http://tcp.cisco-internal.xyz.com">tcp.cisco-internal.xyz.com</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Therefore, the pinpoint subdomain you are creating is: <a target="_blank" href="http://cisco-internal.xyz.com">
cisco-internal.xyz.com</a> on your internal DNS server. This alleviates your need to host
<a target="_blank" href="http://xyz.com">
xyz.com</a> (the parent domain) on your internal DNS, where it would become authoritative and require you to enter every external DNS entry into your internal DNS server.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Excerpt from Jabber DNS Guide, modified to fit your example:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><i>When the client queries the name server for SRV records, it issues additional queries if the name server does not return _cisco-uds or _cuplogin.</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>The additional queries check for the <a target="_blank" href="http://cisco-internal.xyz.com">
cisco-internal.xyz.com</a> pinpoint subdomain zone.</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>For example, Adam McKenzie's services domain is <a target="_blank" href="http://xyz.com">
xyz.com</a> when he starts the client. The client then issues the following query:</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>_cisco-uds._<a target="_blank" href="http://tcp.xyz.com">tcp.xyz.com</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>_cuplogin._<a target="_blank" href="http://tcp.xyz.com">tcp.xyz.com</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>_collab-edge._<a target="_blank" href="http://tls.xyz.com">tls.xyz.com</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>If the name server does not return _cisco-uds or _cuplogin SRV records, the client then issues the following query:</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>_cisco-uds._<a target="_blank" href="http://tcp.cisco-internal.xyz.com">tcp.cisco-internal.xyz.com</a></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i>_cuplogin._<a target="_blank" href="http://tcp.cisco-internal.xyz.com">tcp.cisco-internal.xyz.com</a></i><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Apr 10, 2015 at 9:02 AM Erick Wellnitz <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>> wrote:<o:p></o:p></p>
<p>I understand how to create a pinpoint zone but I'm trying to understand how to create the SRV records for Jabber service discovery based on this example. Do they just get created like:<o:p></o:p></p>
<p><a target="_blank" href="http://Jabber1.xyz.com">Jabber1.xyz.com</a>
zone<br>
Create _cisco-uds._<a target="_blank" href="http://tcp.xyz.com">tcp.xyz.com</a>
under this or will that not give expected behvior?<o:p></o:p></p>
<div>
<p class="MsoNormal">On Apr 10, 2015 4:42 AM, "Justin Steinberg" <<a href="mailto:jsteinberg@gmail.com" target="_blank">jsteinberg@gmail.com</a>> wrote:<o:p></o:p></p>
<p>This is more of a feature of DNS than jabber. <o:p></o:p></p>
<p>See if this blog article helps.<o:p></o:p></p>
<p><a target="_blank" href="http://exchangenerd.com/2014/03/pin-point-dns-split-dns-alternative/">http://exchangenerd.com/2014/03/pin-point-dns-split-dns-alternative/</a><o:p></o:p></p>
<div>
<p class="MsoNormal">On Apr 10, 2015 12:05 AM, "Erick Wellnitz" <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>> wrote:<o:p></o:p></p>
<p>The 10.6 planning guide makes mention of it but only a one liner.<o:p></o:p></p>
<div>
<p class="MsoNormal">On Apr 9, 2015 9:33 PM, "Anthony Holloway" <<a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal">I don't have anything to indicate that it is, or isn't still supported, but I would guess that it would be until we hear an officially announcement and that document get's updated.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I might just fire this up in dCloud and take it for a test drive tomorrow.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Another thing to consider is Jabber via MRA and trying to sign your inside host certs with a public CA. In November of this year (2015), that goes away.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a target="_blank" href="https://www.digicert.com/internal-names.htm">https://www.digicert.com/internal-names.htm</a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you would have had .com externally, and .net internally, then the cert thing doesn't matter, and your question still stands. So, again, I'll see if I can lab it up tomorrow with the latest version of Jabber.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Apr 9, 2015 at 8:54 PM Erick Wellnitz <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Jabber 10.6.2<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have an internal domain (<a target="_blank" href="http://xyz.com">xyz.com</a>)
and an internal domain (xyx.local)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Is the pinpoint subdomain still supported in Jabber 10.6? If not, what are the ramifications to adding
<a target="_blank" href="http://xyz.com">
xyz.com</a> zone to my internal DNS servers?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> The last update of the DNS guide was a year ago.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a target="_blank" href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide_chapter_010.html#CJAB_TK_UEAD61BF_00">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide/CJAB_BK_C606D8A9_00_cisco-jabber-dns-configuration-guide_chapter_010.html#CJAB_TK_UEAD61BF_00</a>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br />
<br />
The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.
<br />
<br />
If you no longer wish to receive commercial messages, you can unsubscribe
by accessing this link: http://www.bennettjones.com/unsubscribe
</body>
</html>