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

SSL VPN, Active Directory and reverse DNS

Hi all,

we're working in an Windows AD environment with about 400 SSL VPN Clients. These are connecting fine and are able to reach all internal services BUT: how do we configure a correctly working reverse DNS?

We've set the request routes so our internal VLANS are resolved forward and backward. All fine.

But if we try to resolve a clients name over it's VPN IP address 10.80.x.x we get a NXDOMAIN error on the UTM.

How do we get the clients to correctly register themselves with our AD based DNS server and in a Reverse Lookup Zone which is hosted there?


This thread was automatically locked due to age.