Score:0

NAT-Reflection on Cisco ASA 5508-X

cn flag

We have 2 internal networks in our environment. 10.1.x as a main network (with different vlans) and 192.168.1.x/24 as WiFi for our travelling users. Both are connected to our Cisco ASA 5508-X and then connected to WAN

Our ERP server provides an app, which contacts a DynDNS Address and is then redirected to our server IP in 10.1.x network. If the app is executed while in 10.1.x networks, it can look up the DNS forward lookup zones in our Active Directory and is then redirected to the internal IP of the server. In the "guest" network 192.168.1.x there is no such zone. I also do not seem to have a possibility to maintain such a host entry in our Cisco 2500 WLC (which would be a solution like the DNS forward lookup zone in AD). Something like DNSMasq, i presume.

Which means, the app contacts the DynDNS Address via WAN and is redirected back. The Cisco ASA seems to judge this as a security risk and denies the connection.

Is it good practice to implement an exception? Or is there a better way?

I am not able to maintain the ASA myself - I have to open a ticket to request changes.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.