Remote Anyconnect client dns IP address and Internet Gateway IP are the same IP 192.168.1.1

[arumugasamy]

Dear Team

Anyconnect client home Internet router gives the IP gateway of 192.168.1.1 and after the client connected to the vpn server got the same IP 192.168.1.1 as DNS IP address.

Now we have to solve the issue not asking the ISP to change their range other than 192.168.1.0/24.

Are there any configuration in the ASA that we can use to change the dns IP address instead of asking internal server team to change the DNS that is also not possible

ASA only we have to find how to change the dns ip address from 192.168.1.1.

[Mike.Cifelli]

Relating to ASA RA VPNs you can apply dns server settings in your Group Policy that gets assigned to your connection profile. Think of the connection profile as the pre-login config and the group policy as the post login config. See screenshot:Then the group policy gets assigned to the respective connection profile you wish to change.  Two other things to note:

1- AFAIK the ASA only supports 2 ipv4 dns servers 

2 - AFAIK the ASA does not support dns through dhcp for AnyConnect clients

HTH!

[arumugasamy]

Dear

you did not understand the issue. Group policy assigned the DNS IP to the remote Anyconnect client but that IP address 192.168.1.1 is conflict with the Gateway IP OF 192.168.1.1 of the client computer because the client PC getting the IP address from the same subnet 192.168.1.0/24 and the gateway of the client PC is 192.168.1.1. So that after Client connected via vpn client Anyconnect DNS ip and local PC gateway IP both are in conflict so that he cannot access the DNS server 192.168.1.1 of their Internal network