You are not logged in.
I am having trouble with a VPN connection not having functioning DNS and I do not know exactly how to trouble shoot it.
Running NetworkManager and installed networkmanager-l2tp, and strongswan. I used the VPN editor in the Gnome and set up the gateway, password authentication, and under IPsec properties I enabled IPsec tunnel L2TP host and used the preshared key.
It connects fine and I can get to IP address but can not use hostnames on the local VPN network. So if i hit 192.168.5.8 it opens the resource but if I try the hostname of that resource it does not open. If i do hostname.domain (domain being my domain name) it will work.
This setup works fine via my windows work machine but when connected to my arch personal machine hostnames only work with the suffix.
What am I missing?
Thanks.
Offline
This sounds very much like a DNS resolver issue.
Whenever DNS resolution fails windows falls back to older methods (with many issues) like NETBIOS.
What are you using for DNS resolution ?
Moderator Note:
Moving to Networking, Server, and Protection
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I am using standard Network Manager package so whatever network manager uses by default. (networking is not my strength).
Thanks
Offline
Is the domain where these hosts are in a public one or one that only exists in your private network ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Its a private company domain. I think it works with the windows work machine on the VPN because its attached to active directory but the Linux machines are not. The article on the Wiki to attach Linux to AD seems very daunting. I was hoping there was a way to tell the traffic going through the VPN to append things with .domain but maybe that is not a thing?
Offline
I think it works with the windows work machine on the VPN because its attached to active directory but the Linux machines are not
It's actually the other way around: Active directory relies on DNS, Kerberos and LDAP and only works if the primary DNS server is properly set (pointing at the DC). So somehow the Windoze VPN client sets the DNS servers correctly.
NetworkManager and it's plugins should™ set the DNS on connecting to the VPN correctly too.
Your "/etc/resolv.conf" should be created by NetworkManager - check it's contents while not and while being connected.
Offline