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.

+++ This bug was initially created as a clone of Bug #2006761 +++

Description of problem:

systemd-resolved always (reverse)-resolves the host's IP addresses and FQDN.
This can be harmful when an application (for instance, a DNS zone manager) is installed on the same server instance.
That application would expect NXDOMAIN to be returned if the current server's IP does not belong in an already managed reverse zone.

More details:
https://lists.freedesktop.org/archives/systemd-devel/2021-September/046856.html


How reproducible:

Always, see list post.



Expected results:

Being able to disable the generation of synthetic RRs.


Additional info:

The workarounds described in the mailing-list all imply changing the application in a more or less intrusive or fragile way. Being able to change resolved's behavior in its configuration file would be much more efficient.

Hi François,

with systemd 250, there is a $SYSTEMD_NSS_RESOLVE_SYNTHESIZE for resolvers using libnss.

Just a quick recap, for the systemd 250 host with address 192.168.254.2:

SYSTEMD_NSS_RESOLVE_SYNTHESIZE=1 getent -s hosts:resolve hosts 192.168.254.2; echo $?
192.168.254.2   host2006762 host2006762.local
0

[root@host2006762 ~]# SYSTEMD_NSS_RESOLVE_SYNTHESIZE=0 getent -s hosts:resolve hosts 192.168.254.2; echo $?
2

Looking at a sibling Bug 2006761, I propose to close this bug.

Hi Jacek,

I created the RHEL9 bug to make sure that systemd-resolved would not be shipped in RHEL9 without this fix.
I'll defer to Antonio (CC'd) to decide whether closing is acceptable for FreeIPA/Identity Management.

Thanks!
François

This issue should be fixed via rebase to systemd v252.

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:2531