<div dir="ltr">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><div><br></div><div><br></div><div>I don't see a query for <a href="http://cisco-internal.xyz.com">cisco-internal.xyz.com</a><br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 10, 2015 at 8:09 AM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">According to the document you linked, Jabber will first perform this query:<br><br>_cisco-uds._<a href="http://tcp.xyz.com" target="_blank">tcp.xyz.com</a><div><br></div><div>If nothing comes back, then it will try:</div><div><br></div><div>_cisco-uds._<a href="http://tcp.cisco-internal.xyz.com" target="_blank">tcp.cisco-internal.xyz.com</a></div><div><br></div><div>Therefore, the pinpoint subdomain you are creating is: <a href="http://cisco-internal.xyz.com" target="_blank">cisco-internal.xyz.com</a> on your internal DNS server. This alleviates your need to host <a href="http://xyz.com" target="_blank">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.</div><div><br></div><div>Excerpt from Jabber DNS Guide, modified to fit your example:</div><div><br></div><div><div><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></div><div><i><br></i></div><div><i>The additional queries check for the <a href="http://cisco-internal.xyz.com" target="_blank">cisco-internal.xyz.com</a> pinpoint subdomain zone.</i></div><div><i><br></i></div><div><i>For example, Adam McKenzie's services domain is <a href="http://xyz.com" target="_blank">xyz.com</a> when he starts the client. The client then issues the following query:</i></div><div><i>_cisco-uds._<a href="http://tcp.xyz.com" target="_blank">tcp.xyz.com</a></i></div><div><i>_cuplogin._<a href="http://tcp.xyz.com" target="_blank">tcp.xyz.com</a></i></div><div><i>_collab-edge._<a href="http://tls.xyz.com" target="_blank">tls.xyz.com</a></i></div><div><i><br></i></div><div><i>If the name server does not return _cisco-uds or _cuplogin SRV records, the client then issues the following query:</i></div><div><i>_cisco-uds._<a href="http://tcp.cisco-internal.xyz.com" target="_blank">tcp.cisco-internal.xyz.com</a></i></div><div><i>_cuplogin._<a href="http://tcp.cisco-internal.xyz.com" target="_blank">tcp.cisco-internal.xyz.com</a></i></div></div></div><br><div class="gmail_quote">On Fri, Apr 10, 2015 at 9:02 AM Erick Wellnitz <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">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:</p>
<p dir="ltr"><a href="http://Jabber1.xyz.com" target="_blank">Jabber1.xyz.com</a> zone<br>
Create _cisco-uds._<a href="http://tcp.xyz.com" target="_blank">tcp.xyz.com</a> under this or will that not give expected behvior?</p>
<div class="gmail_quote">On Apr 10, 2015 4:42 AM, "Justin Steinberg" <<a href="mailto:jsteinberg@gmail.com" target="_blank">jsteinberg@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">This is more of a feature of DNS than jabber. </p>
<p dir="ltr">See if this blog article helps.</p>
<p dir="ltr"><a href="http://exchangenerd.com/2014/03/pin-point-dns-split-dns-alternative/" target="_blank">http://exchangenerd.com/2014/03/pin-point-dns-split-dns-alternative/</a></p>
<div class="gmail_quote">On Apr 10, 2015 12:05 AM, "Erick Wellnitz" <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">The 10.6 planning guide makes mention of it but only a one liner.</p>
<div class="gmail_quote">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:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.<div><br></div><div>I might just fire this up in dCloud and take it for a test drive tomorrow.<br><div><br></div><div>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.</div><div><br></div><div><a href="https://www.digicert.com/internal-names.htm" target="_blank">https://www.digicert.com/internal-names.htm</a><br></div></div><div><br></div><div>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.</div></div><br><div class="gmail_quote">On Thu, Apr 9, 2015 at 8:54 PM Erick Wellnitz <<a href="mailto:ewellnitzvoip@gmail.com" target="_blank">ewellnitzvoip@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Jabber 10.6.2</div><div><br></div><div>I have an internal domain (<a href="http://xyz.com" target="_blank">xyz.com</a>) and an internal domain (xyx.local)</div><div><br></div><div>Is the pinpoint subdomain still supported in Jabber 10.6? If not, what are the ramifications to adding <a href="http://xyz.com" target="_blank">xyz.com</a> zone to my internal DNS servers?</div><div><br></div><div> The last update of the DNS guide was a year ago.</div><div><br></div><div><a 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" target="_blank">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> </div><div><br></div><div>Thanks!</div></div>
______________________________<u></u>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/<u></u>mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
</blockquote></div>
<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 href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div><br></div>