Internal DNS Not Resolving - Fedora 35
I know there's been a couple issues on this - but I did a deep dive trying to fix this and I found a workaround. Maybe this can be fixed in another update?
For background, my company uses split-dns and split-tunneling. Unsure whether that was the cause of the issue, but this is what I found.
When I attempted to use openfortivpn on Fedora 35, I ran into the problems with systemd resolving dns with openfortivpn. This lead me to this project.
When the NetworkManager-fortisslvpn, in order to resolve my private and public DNS, I had to select "use this connection only for resources on its network" because my organization black holes traffic not destined for the private network when sent over the tunnel. However, after doing this, for some reason my requests for DNS still went over my local interface. I had to run systemd-resolve --interface ppp0 --set-dns 1.2.3.4 --set-domain domain.com
as seen in another issue. I can now resolve private dns and public dns and navigate to both public and private resources when connected to my VPN.
I know this was a long issue, and maybe not the most well articulated. I'm posting some evidence of the problem below, and if you need anything else from me to help diagnose the issue for a future fix, please let me know!
Before setting systemd-resolve for ppp0 to my domain & dns IP:
resolvectl dns
Global:
Link 2 (wlp0s20f3): 75.75.75.75 75.75.76.76 2001:558:feed::1 2001:558:feed::2
Link 26 (ppp0):
After setting systemd-resolve for ppp0
resolvectl dns
Global:
Link 2 (wlp0s20f3): 75.75.75.75 75.75.76.76 2001:558:feed::1 2001:558:feed::2
Link 26 (ppp0): 1.2.3.4
I'll do more testing and make sure it works, but it appears to be good so far.