The issue I raised upstream has now been closed [1], after Roy produced a new
release of openresolv [2] with support for systemd-resolved.
Unfortunately, IMHO the direction taken in openresolv doesn't help us much with
the present bug, for the following reasons:
- It violates the principle of
Hi Ken,
Thanks for raising this, I've had a hunch things are still a bit dodgy in
this area for a while now.
I'm overall not very happy with Debian's DNS configuration story and I've
been meaning to have a go at improving the situation, but so far I haven't
been able to focus on it.
If you want
Further to our upstream discussion at [1] I have raised wishlist Bug#1103785
[2] for systemd-resolved.
With trixie release coming up, I would not expect to see any enthusiasm for
making these sorts of changes across multiple packages.
For now I guess you have the option of patching the hook scr
On 21/04/2025 06:04, Martin-Éric Racine wrote:
> Hey Ken,
>
>
> Thanks for this bug report and very thorough analysis.
>
> Can you submit a report upstream and link to this bug?
>
> https://github.com/NetworkConfiguration/dhcpcd/issues/new
>
> Martin-Éric
I have done so: https://github.com/Ne
Hey Ken,
ma 21.4.2025 klo 1.42 Ken Milmore (ken.milm...@gmail.com) kirjoitti:
>
> Package: dhcpcd-base
> Version: 1:10.1.0-9
>
> Description:
>
> When using dhcpcd-base together with systemd-resolved, the name server
> settings for an interface are initially configured correctly from DHCP but
>
Package: dhcpcd-base
Version: 1:10.1.0-9
Description:
When using dhcpcd-base together with systemd-resolved, the name server settings
for an interface are initially configured correctly from DHCP but may then
subsequently disappear, leaving no DNS server configured.
This is because the dhcpcd
6 matches
Mail list logo
