Last week, we've enabled our Microsoft DNS to permit the registration of clients. (For some reason this feature was not enabled) Now we've noticed some strange but understandable behavior when our remote users login to anyconnect,
Joe Buck logs into our any connect portal from home, is given an IP address from our ASA set pool say 172.30.1.20, his DNS is set to 172.31.16.140, 172.31.16.30. Joe does a nslookup 172.30.1.20 from his home PC and the result shows jbuck-homePC. Joe is running a Windows7 client.
Joe disconnects from his session and Jane Doe logs in likewise. Jane receives the IP address 172.30.1.20 and her DNS servers are set likewise 172.31.16.140 and 172.31.16.30. Jane executes the command from her home computer the nslookup 172.30.1.20 and receives the response jbuck-homePC.
This is an issue that I'm trying to resolve. I'm thinking that Joe has his computer to register with DNS and Jane does not. Regardless I'm looking for a resolve where for instance if Joe Buck woould terminate his SSL VPN session, our internal DNS would flush his DNS record.
Thought 1) Would Cisco have any command that I might be missing that can be set on the VPN config file?
Thought 2) Can I setup my ASA to pull addresses from my inside DHCP server from a specific scope?
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...