dhclient overriding stub-resolv.conf file on Jammy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
isc-dhcp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Issue]
On Jammy, the stub-resolv.conf file on /run/systemd/
While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-
[Reproducer]
-
I used a cloud-image based Jammy installation (uvt-kvm). Once in:
$ cat /run/system/
And one will see:
nameserver 127.0.0.53
options edns0 trust-ad
search .
Then:
$ sudo dhclient
$ cat /run/system/
You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed.
[Impact]
This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances.
[Extra]
-
As a minor test, I copied over the dhclient-
[ . . . ]
Let me know if further clarification is needed to proceed. Thank you.
BR,
pprincipeza
[0] https:/
[1] https:/
[2] https:/
tags: | added: sts sts-sponsor-halves |
tags: | added: rls-jj-incoming |
tags: | added: fr-2552 |
tags: | removed: rls-jj-incoming |
tags: | removed: sts sts-sponsor-halves |
Status changed to 'Confirmed' because the bug affects multiple users.