On Thu, Dec 05, 2024 at 08:11:50 +0100, Ben Boeckel wrote:
> At $DAYJOB, we started migrating to 2FA for VPN which has caused me to
> look at how I can get the system service to provoke my user session to
> ask me a prompt for the password. Of course, systemd has a solution for
> it that:
>
>
> My DNS servers are currently manually specified in
> /etc/systemd/network/10-ens.network as follows:
>
> [Match]
> Name=en*
> [Network]
> DHCP=ipv4
> DNS=first-server-ip-goes-here
> DNS=second-server-ip-goes-here
> DNS=third-server-ip-goes-here
> [DHCPv4]
> UseDNS=false
> UseNTP=false
> [IPv6Acc
On Mon, Dec 23, 2024, at 09:09, Laura Smith wrote:
> Sent with Proton Mail secure email.
>
> On Monday, 23 December 2024 at 14:00, Kevin P. Fleming
> wrote:
>
>> The simplest fix is to set "DNSSEC=no"
>
> That seems to me to be a bit of a "sledgehammer to crack a nut".
>
> The man page for resol
On Mon, Dec 23, 2024, at 08:37, Laura Smith wrote:
> Sent with Proton Mail secure email.
>
> On Monday, 23 December 2024 at 12:23, Adam Nielsen
> wrote:
>
>> But what's the underlying issue? Maybe there's a different fix?
>
> Its been a while so I can't remember the exact details, but I know its
Sent with Proton Mail secure email.
On Monday, 23 December 2024 at 14:00, Kevin P. Fleming
wrote:
> The simplest fix is to set "DNSSEC=no"
That seems to me to be a bit of a "sledgehammer to crack a nut".
The man page for resolved.conf says:
"It is recommended to set DNSSEC= to true on
On Monday, 23 December 2024 at 13:10, Itxaka Serrano Garcia
wrote:
> Hallo there!
>
> If using systemd-resolved, cant you just configure the DNS in
> /etc/systemd/resolved.conf or /etc/systemd/resolved.conf.d/ directly so it
> setups your desired address?
My DNS servers are currently manu
Sent with Proton Mail secure email.
On Monday, 23 December 2024 at 12:23, Adam Nielsen
wrote:
> But what's the underlying issue? Maybe there's a different fix?
Its been a while so I can't remember the exact details, but I know its to do
with Postfix.
Postfix creates a copy (not symlin
On Mon, Dec 23, 2024 at 11:08:56AM +, Laura Smith wrote:
> > I believe you can just remove the symlink at /etc/resolv.conf and
> > replace it with a file that points to 127.0.0.54.
> Thanks Daniel, that has been my work-around, a systemd timer checking for
> 127.0.0.53 and doing a sed on /etc/
Hallo there!
If using systemd-resolved, cant you just configure the DNS in
/etc/systemd/resolved.conf or /etc/systemd/resolved.conf.d/ directly so it
setups your desired address?
If using any other resolver/network manager, just remove the symlink from
/etc/resolv.conf to the systemd resolv.conf s
> Thanks Daniel, that has been my work-around, a systemd timer checking
> for 127.0.0.53 and doing a sed on /etc/resolv.conf
>
> So I came here looking for a more "official" work-around, e.g. some
> config file param I missed.
>
> But it looks like there isn't, so I guess I'll just leave my
> wor
On Monday, 23 December 2024 at 07:45, Daniel Foster wrote:
> I believe you can just remove the symlink at /etc/resolv.conf and
> replace it with a file that points to 127.0.0.54.
>
Thanks Daniel, that has been my work-around, a systemd timer checking for
127.0.0.53 and doing a sed on /etc/re
11 matches
Mail list logo
