RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2161260 - resolvectl dns does not display localhost as Global DNS server
Summary: resolvectl dns does not display localhost as Global DNS server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: systemd
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jacek Migacz
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On: 2148870
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-16 12:14 UTC by Jacek Migacz
Modified: 2023-11-07 11:31 UTC (History)
15 users (show)

Fixed In Version: systemd-252-18.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2148870
Environment:
Last Closed: 2023-11-07 08:54:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel9 pull 185 0 None open (#2161260) display localhost as Global DNS server 2023-07-29 20:11:13 UTC
Red Hat Issue Tracker RHELPLAN-145190 0 None None None 2023-01-16 12:17:13 UTC
Red Hat Product Errata RHBA-2023:6640 0 None None None 2023-11-07 08:54:28 UTC

Description Jacek Migacz 2023-01-16 12:14:01 UTC 
+++ This bug was initially created as a clone of Bug #2148870 +++

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

--- Additional comment from Zbigniew Jędrzejewski-Szmek on 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

--- Additional comment from Florence Blanc-Renaud on 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.

--- Additional comment from Jacek Migacz on 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 8 errata-xmlrpc 2023-11-07 08:54:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6640
Note You need to log in before you can comment on or make changes to this bug.