Thank you!
On Wed Sep27'23 03:04:53PM, Samuel Sieb wrote:
From: Samuel Sieb <samuel(a)sieb.net>
Date: Wed, 27 Sep 2023 15:04:53 -0700
To: users(a)lists.fedoraproject.org
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Subject: Re: F38: systemd-resolved.service oddity
On 9/27/23 09:14, Ranjan Maitra wrote:
> From the past week, I have had an issue in that after several hours, some
particular sites become inaccessible to me, and can only be accessed if I use restart
using sudo systemctl restart systemd-resolved.service
>
> What particular issues cause this? Why did it start a week ago, and has become
quite reliable in its annoyance? (I have to say that when I can no longer access this
site, I am no longer on Cisco SecureClient VPN, which is also one of the sites which can
not be accessed with Cisco SecureClient VPN without restarting systemd-resolved.service,
and the site is my worksite domain).
That is probably relevant. resolved supports split DNS when using a
VPN.
I think so too!
Try the following commands both while the VPN is running and then
after you
stop it:
resolvectl dns
resolvectl domain
while running:
$ resolvectl dns
Global: [IP addresses associated with my VPN site] {*}
Link 2 (enp57s0u2u1u1): [IP addresses associated with my ISP] 192.168.1.1 {**}
Link 22 (cscotun0):
$ resolvectl domain
Global: [VPN connection domainname] [ISP]
Link 2 (enp57s0u2u1u1): [ISP]
Link 22 (cscotun0):
where [VPN connection] stands for the address that is associated with VPN.
After stopping VPN:
$ resolvectl dns
Global: [Same as {*}]
Link 2 (enp57s0u2u1u1): [Same as {**}]
$ resolvectl domain
Global: [VPN connection domainname] [ISP]
Link 2 (enp57s0u2u1u1): [ISP]
After $ sudo systemctl restart systemd-resolved.service
$ resolvectl dns
Global:
Link 2 (enp57s0u2u1u1): [Same as {**}]
$ resolvectl domain
Global:
Link 2 (enp57s0u2u1u1): [ISP]
Seems to me there is something "sticky" about the VPN connection?
Many thanks for your suggestions and help!
Best wishes,
Ranjan