* Systemd-resolved problem
@ 2022-03-19 14:20 Barry Cisna
2022-03-22 9:35 ` Robert Sander
0 siblings, 1 reply; 2+ messages in thread
From: Barry Cisna @ 2022-03-19 14:20 UTC (permalink / raw)
To: wireguard
Hello,
Newbie to Wireguard,
1- Server VPS in Google Cloud Debian Bullseye,
2- Home Server Debian Bullseye , behind CGNAT.
After many hours trying to get this to work,,here is situation, from
'client' server2 i can ping any external /internet ip address, i
cannot web browse/ resolve names. Have tried multiple iptables
examples.
So now find that when i do an sudo wg-quick up <wg0>
systemd-resolved.service is in a 'degraded state'. As soon as i down
the wg0 the systemd-resolved service is running normally again
when doing a resolvectl with the wg0 interface up there are no dns
servers on the wg0 interface
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Systemd-resolved problem
2022-03-19 14:20 Systemd-resolved problem Barry Cisna
@ 2022-03-22 9:35 ` Robert Sander
0 siblings, 0 replies; 2+ messages in thread
From: Robert Sander @ 2022-03-22 9:35 UTC (permalink / raw)
To: wireguard
Am 19.03.22 um 15:20 schrieb Barry Cisna:
> when doing a resolvectl with the wg0 interface up there are no dns
> servers on the wg0 interface
Where should they come from?
Do you have the default route through your Wireguard tunnel?
Then systemd-resolved likely will not be able to reach the DNS resolvers
any more. You will have to configure resolvers that are reachable
through the Wireguard tunnel (e.g. 9.9.9.9 or similar).
Regards
--
Robert
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-04-22 0:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-19 14:20 Systemd-resolved problem Barry Cisna
2022-03-22 9:35 ` Robert Sander
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).