F5F Stay Refreshed Power Users Networks DNS problems in the VPN subnet (Lab Net functions properly)

DNS problems in the VPN subnet (Lab Net functions properly)

DNS problems in the VPN subnet (Lab Net functions properly)

J
JayCraft621
Junior Member
20
02-03-2016, 01:36 AM
#1
Sorry for the title, I wasn't sure what would be the best name. I start by clarifying: My VPN server is on 10.145.30.2 (10.145.30.0/24), my lab server runs at 10.145.50.6 (10.145.50.0/24), and my DNS servers are at 10.0.0.3 and 10.0.0.4. Both the VPN and lab can reach the DNS without issues, and nslookup functions properly. The odd occurrence is when a friend connects via VPN to my VPN network and gets a 10.145.30.x IP address. After a short delay, his nslookup requests stop and the DNS server shows an error instead of the correct name. When he tries to query the lab server, everything works fine. Changing the subnet so the VPN server can assign IPs to the lab network resolves the problem. My firewall rules for the VPN network match those on the lab network. The issue seems to be isolated to the VPN network itself. Is there anything else you'd like to investigate?

Your CMD links and the ocserv software are functioning correctly, except during this specific scenario. I've already reported the issue on GitLab, but it was closed as a client-side problem. You can find the open issue here: https://gitlab.com/openconnect/ocserv/-/issues/395
J
JayCraft621
02-03-2016, 01:36 AM #1

Sorry for the title, I wasn't sure what would be the best name. I start by clarifying: My VPN server is on 10.145.30.2 (10.145.30.0/24), my lab server runs at 10.145.50.6 (10.145.50.0/24), and my DNS servers are at 10.0.0.3 and 10.0.0.4. Both the VPN and lab can reach the DNS without issues, and nslookup functions properly. The odd occurrence is when a friend connects via VPN to my VPN network and gets a 10.145.30.x IP address. After a short delay, his nslookup requests stop and the DNS server shows an error instead of the correct name. When he tries to query the lab server, everything works fine. Changing the subnet so the VPN server can assign IPs to the lab network resolves the problem. My firewall rules for the VPN network match those on the lab network. The issue seems to be isolated to the VPN network itself. Is there anything else you'd like to investigate?

Your CMD links and the ocserv software are functioning correctly, except during this specific scenario. I've already reported the issue on GitLab, but it was closed as a client-side problem. You can find the open issue here: https://gitlab.com/openconnect/ocserv/-/issues/395

C
Camillah
Member
68
02-11-2016, 01:19 AM
#2
Still no answer in sight. It’s truly remarkable. If anyone discovered a fix, I’d love to hear about it.
C
Camillah
02-11-2016, 01:19 AM #2

Still no answer in sight. It’s truly remarkable. If anyone discovered a fix, I’d love to hear about it.