6/11/2023 0 Comments Ubuntu fortinet vpn client![]() On the other hand, resolvectl query uses all other addresses for source IP except the one assigned by VPN. It turned out that nslookup uses a VPN assigned address for the source IP when asking DNS for a name. Since this was strange I traced network traffic to see what does nslookup differently than resolvectl query. ![]() If I try with nslookup like this nslookup Strange thing is that when I write resolvectl query Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLSĭNS Servers: 172.20.1.16 172.20.1.21 2a00:ee0:d::13 2a00:ee0:e::13Īs you can see additional DNS servers are added to Link 3, which should help me resolve internal names when connected to VPN. Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupportedĭNS Servers: 192.168.1.1 2a00:ee0:d::13 2a00:ee0:e::13Īfter VPN is established resolvectl reports additional link called vpn: resolvectl Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported This is output from resolvectl before VPN is established: resolvectl I am using Ubuntu 22.04, which is not an official version yet, but I have doubts it will get any better until official release in a week or two. It may be FortiClient VPN, systemd-resolved, or something else. Unfortunately, I have no idea, who's fault is that. After spending some time, I figured out that DNS is not working as it should have. I have a strange problem when I connect to a company VPN with forticlient application.
0 Comments
Leave a Reply. |