Service discovery without split-horizon DNS

[Fred Nielsen (ePlus)]

When the current Jabber suites find a valid _cisco-uds SRV record, they attempt to connect to on-premise IM&P services - this is the documented and expected behavior.

However, for customers that do not leverage a split-horizon (aka split-brain) DNS infrastructure along with MRA, this presents a significant problem.  External clients can see the internal SRV record, and further it appears that the clients do not fail back to attempting an external connection when the internal connectivity fails.  The Jabber deployment guides talking about non split-brain DNS, but don't really address what to do about it.

Is there any way to workaround this?

[Wing Yin MO]

Fred:

I have setup the _collab-edge._tls.domain only,

~root to VCS control that doing the uds lookup.

vi dnsmasq.conf,

add
# Two SRV records for UDS, each with different priorities
srv-host=_cisco-uds._tcp.domain,cucm.domain,8443,1

only issue is that all jabber clients are now logged in via expressway... with the jabber limitation for expressway.. single line/uds etc.