ASA and Dynamic DNS Question

[Craddockc]

Community,

I'm experiencing the following issue:

Anyconnect VPN clients get their DHCP settings from the Cisco ASA via the VPN group policy and not from a back end windows server. What were noticing is that the "A" Records in our  Windows DNS for the VPN clients are updating fine, but the "PTR" records (for reverse lookups) for the same clients are all over the place. As the VPN clients connect, getting IP addresses and other settings from the ASA, it doesn't appear as though the "PTR" records in our DNS servers are being updated with any regularity.

From what I am reading, normally the DHCP server is supposed to handle the function of updating the "PTR" records, while the Clients will update the "A" record. The clients that do get their DHCP settings from our Windows Servers have up to date PTR information in DNS, which leads me to believe that maybe the Firewall isn't updating the DNS properly

Does anyone know how the Cisco ASA goes about updating the DNS servers of the client IP's and hostnames it gave address settings to? We do not have DHCP enabled on any of the interfaces, Just pools set up in the VPN Group Policy profiles. 

Thanks.

[Marius Gunnerud · Accepted solution]

The short answer is that the ASA does not send updates to DNS server.

We had this same issue where we had a requirement for some proprietary software that require reverse lookup.  We had to move all our VPN locally defined pools to the centralized DHCP server to get this working.

[Craddockc]

Thank you Marius! I believe this is also what we will need to do as well.