Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why do we need to bind a Dyndns to an interface?

I'm trying to configure a Dyndns hostname that must be valid either when the link 1 OR link 2 is up, but the Dynamic DNS configuration requires the hostname to be bound to an interface.

It's only useful to know the IP address of a specific interface, but we have to check link 1 and link 2 to see which one is up before trying a connection, e.g., establishing a VPN tunnel.

As we also don't have anymore the High Availability definition, we can't automate this check in the client side.

Does anyone know how to accomplish this?

[]s, MM



This thread was automatically locked due to age.
Parents Reply Children
No Data