10-25-2021 03:54 AM
Does the internal and external dns for expway e must have the same domain name? I have configured dual nic on E. And traversal zone is working but jabber can't connect to internal server.
10-25-2021 04:06 AM - edited 10-25-2021 04:11 AM
Hello,
what you mean with dns?
The configured DNS-servers in EXP-E? Or the DNS-names of EXP-E?
As far as I have in my head, the EXP-E the only DNS-entries that it needs to resolve for MRA to work is it's own A-record and the corresponding PTR at your public DNS-provider.
The most that you my have to be sure is, that EXP-E can resolve the A-Record and PTR of EXP-C too.
So for MRA, it would then need an internal DNS-server, that can resolve the EXP-C related DNS-entries.
10-25-2021 04:11 AM
Its not mandatory to have the same domain. I have customer using MRA feature who's Internal and external domains are different.
Take logs from Both E and C and run it on CSA tool. Its give you more information.
You can access CSA tool from https://cway.cisco.com/csa/
Detailed steps to collect the logs has been mentioned on below document.
10-25-2021 10:47 AM
Hello @plp_pnlr
Does the internal and external dns for expway e must have the same domain name?
Domain name in DNS Server with MRA can working with same domain or with different domain like expe.local - expe.com or expe.com(internal) - expe.com (external) - SRV cisco-uds for internal and collab-edge for external .
but insure from domain is configured correctly in expe (expe.com as external)
Best Regards
10-25-2021 07:59 PM
Hi Mahmoud,
is there a way in expe to identify if its for external? because on Domains you can add domain names?
10-25-2021 09:09 PM
Assume that your internal domain as abc.local and external domain as abc.com.
Configure Expressway-C System>> Dns :-
10-26-2021 01:19 AM
on CSA, it says no issues were found. but jabber recieves 'can't communicate with the server' error. on Configuration>domains, do I need to add both internal and external domains? and in exp-C zones>peer address, do I need to put also the exp-eexternal address? b'cause I think it should be only the internal address.
10-26-2021 01:58 AM
Assuming, you have split DNS internally, under "configuration --> domains" you need to set all external domains, for which the users login from external via MRA.
Taking Nithin's example: "abc.com".
Exp-C then needs to resolve the SRV "_cisco-uds._tcp.abc.com" via it's internal DNS server.
Under "Exp-C zones --> peer address" it depends what you need to set.
If Exp-C can resolve the external FQDN of EXP-E, then you can set this as peer address.
If it only can resolve the internal FQDN of EXP-E, then you can set this as peer address.
If it can resolve both, then you can choose.
But: whatever FQDN you choose, it has to be in the certificate of the EXP-E!!!
If it isn't, you get a TLS connection error.
Note:
Some of the public CA's don't accept internal domains in the CSR's.
Therefore, the only option is to use an external FQDN in the cert of EXP-E --> therefore, the peer address in EXP-C also needs to point to the external FQDN.
10-26-2021 02:54 AM
Lets Assume,
On internal DNS:-
Domain abc.local
A-record :- express-C.abc.local 192.168.10.10
Domain abc.com (sub zone)
A-record :- express-E.abc.com 192.168.10.11
Public DNS:-
A-record :- express-E.abc.com 72.72.72.11
_collab-edge._tls.abc.com SRV service location: priority = 3 weight = 7 port = 8443 svr hostname = express-E.abc.com
Configure Expressway-C System>> Dns :-
04-04-2022 03:02 AM
Regarding the certificate, Is it the expressway E has to add on FQDN expressway C ? if yes, the Public CA no accept the internal domain name.
04-04-2022 03:15 AM - edited 04-04-2022 03:15 AM
Expressway E certificate must contain the external domain as the dns field.
when generating csr add this files as dns.
there is no need to add the expressway c details on E certificate.
10-31-2021 09:09 PM
The problem is now solved. Not only the FQDN of exp-E must be on its certificate but also the domain name of public DNS. also tcp was not enabled on the MRA setting. Thank you all for your help.
11-01-2021 01:02 AM
Yes always the issue happened with
FQDN you choose, it has to be in the certificate.
If it isn't, you get a TLS connection error.
best regards and aorry for late
04-04-2022 03:00 AM
is it missing the FQDN for express C when generate CSR on Expressway E ?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide