Webex Calling - Registrar and Outbound Proxy names don't resolve

[TONY SMITH]

Hi,

I'm trying to setup a local gateway, and one immediate barrier that I think I face is that neither the Registrar Domain, nor in particular the Outbound Proxy name can be resolved by any DNS that I have tried.

Surely this is incorrect, I don't see how a proxy can be used if it can't be resolved.

Or am I missing something fundamental.

[TONY SMITH]

What's a bit odd is that the gateway keeps trying and failing to establish TCP to 139.177.67.10 which is within one of the Webex prefixes, but I can't see how that's being resolved.  There don't seem to be any DNS look ups happening.

The connection doesn't establish, it goes through the three way handshake then goes into various wait and timeout states.  It never makes it to TLS, but these was two way communications before it gives up.

So I don't really know if there are other issues, but at least if I could confirm the DNS question that's one thing out of the way.

[TONY SMITH · Accepted solution]

OK it must resolve by magic I think, because it's now registered even though no DNS server in the world resolves that proxy as a host name.  Is the CUBE maybe doing an SRV lookup of some sort?  I can't catch it at it, I've not seen any DNS at all in the packet captures.