mcannon-gso
New Around Here
Good Day All..
I have been chasing an issue with DNS where on the cmd line from the router DNS could not resolve addresses. Also the check for update was not working correctly and the VPN status page had an extreme lag to it..
My setup is as follows.. DNS/DHCP is provided by a windows server on my network. I have separate IP address ranges for my guest network performed by scripting dnsmasq for the gust network interfaces and I am running a client VPN to a service.
In my investigations I found that by using the "Accept DNS Configuration" (Strict) the actual /tmp/resolv.conf file was created with 4 entries. The first 2 being DNS from the VPN and the last 2 being the DNS addresses I provided on the WAN page. So every local resolution would first try to resolve to the VPN DNS servers which are only accessible to the clients connected to the VPN via the "Routing Policy" (strict). So this was causing issues.
When I turned "Accept DNS Configuration" to disabled, the 2 VPN DNS servers were removed and the 2 from the WAN remained. Now pings from command line, Update check and ping from the GUI all work as expected. The lag from the VPN status page was also eliminated..
Not sure if this was an intended function or a possible bug, however, I wanted to touch on it in case anyone else is experiencing the same issues.
Any and all comments are welcomed..
--mcannon-gso
I have been chasing an issue with DNS where on the cmd line from the router DNS could not resolve addresses. Also the check for update was not working correctly and the VPN status page had an extreme lag to it..
My setup is as follows.. DNS/DHCP is provided by a windows server on my network. I have separate IP address ranges for my guest network performed by scripting dnsmasq for the gust network interfaces and I am running a client VPN to a service.
In my investigations I found that by using the "Accept DNS Configuration" (Strict) the actual /tmp/resolv.conf file was created with 4 entries. The first 2 being DNS from the VPN and the last 2 being the DNS addresses I provided on the WAN page. So every local resolution would first try to resolve to the VPN DNS servers which are only accessible to the clients connected to the VPN via the "Routing Policy" (strict). So this was causing issues.
When I turned "Accept DNS Configuration" to disabled, the 2 VPN DNS servers were removed and the 2 from the WAN remained. Now pings from command line, Update check and ping from the GUI all work as expected. The lag from the VPN status page was also eliminated..
Not sure if this was an intended function or a possible bug, however, I wanted to touch on it in case anyone else is experiencing the same issues.
Any and all comments are welcomed..
--mcannon-gso
