Bug 2148870 - resolvectl dns does not display localhost as Global DNS server
Summary: resolvectl dns does not display localhost as Global DNS server
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jacek Migacz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2161260
TreeView+ depends on / blocked
 
Reported: 2022-11-28 08:48 UTC by Florence Blanc-Renaud
Modified: 2023-04-19 19:26 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
: 2161260 (view as bug list)
Environment:
Last Closed: 2023-04-19 19:26:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd systemd pull 25929 0 None Merged resolvectl: show 127.0.0.1 among global DNS servers again 2023-01-16 12:27:04 UTC

Description Florence Blanc-Renaud 2022-11-28 08:48:16 UTC 
Description of problem:
The behavior of the command "resolvectl dns" has changed with systemd-resolved-252.2-591 and does not display the local host as Global DNS server even though a config file /etc/systemd/resolved.conf.d/zzz-ipa.conf is setting DNS=127.0.0.1

Version-Release number of selected component (if applicable):
systemd-resolved-252.2-591.fc38.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Install freeipa-server on a host named server.ipa.test:
# dnf install -y freeipa-server-dns
# ipa-server-install --domain ipa.test --realm IPA.TEST --setup-dns --auto-forwarders -a Secret123 -p Secret123 -U

2. Check the content of the configuration files:
# cat /etc/systemd/resolved.conf | grep -v '^#'

[Resolve]
# cat /etc/systemd/resolved.conf.d/zzz-ipa.conf  | grep -v '^#'

[Resolve]
DNS=127.0.0.1
Domains=~. ipa.test

3. Check the output of resolvectl dns:
# resolvectl dns
Global:                                   <<<<< here we expect to see 127.0.0.1
Link 2 (eth0): 10.11.5.160 10.2.70.215

Actual results:
Even though the config file defines the localhost as DNS server, "resolvectl dns" does not show the localhost as global DNS server.

Expected results:
With the previous version of systemd-resolved (systemd-resolved-252.1-588.fc38.x86_64), the localhost was shown:

# resolvectl dns
Global: 127.0.0.1
Link 2 (eth0): 10.11.5.160 10.2.70.215
Comment 1 Zbigniew Jędrzejewski-Szmek 2022-12-08 21:53:11 UTC 
You say 252.2 is the first bad. Was this a regression after 252.1?

Jacek, any idea what is going on here?
I see the following patches in that range:
$ git lol v252.1..v252.2 src/resolve/
* 595dd9b2b9 resolved: Fix OpenSSL error messages
* d337ac02d6 resolved: when configuring 127.0.0.1 as per-interface DNS server, contact it via "lo" always
* 813d52dbf8 resolved: use right conditionalization when setting unicast ifindex on UDP sockets
Comment 2 Florence Blanc-Renaud 2022-12-12 14:53:03 UTC 
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1)
> You say 252.2 is the first bad. Was this a regression after 252.1?

Yes, 252.1-588 did not show the issue, 252.2-591 shows the issue.
Comment 3 Jacek Migacz 2022-12-20 14:21:46 UTC 
I've put it back in the PR, but I'm not sure about the logic there.
Comment 4 Ben Cotton 2023-02-07 15:13:36 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.
Comment 5 Florence Blanc-Renaud 2023-04-19 09:23:30 UTC 
FYI, our tests don't see the issue any more, using systemd-resolved-253~rc2-2.fc38.x86_64 and above.
Comment 6 Jacek Migacz 2023-04-19 19:26:21 UTC 
Thanks Florence.
Note You need to log in before you can comment on or make changes to this bug.