Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-92602

NetworkManager does not update DNS when routes are created

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-10.0
    • NetworkManager
    • None
    • No
    • None
    • rhel-net-mgmt
    • ssg_networking
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      Given a host running NetworkManager with systemd-resolved or dnsmasq, and a DHCP lease that provides identical DNS servers but later changes the per-link routes those servers rely on,

      When NM processes the renewed lease,

      Then NM must regenerate the DNS configuration and the new reverse-DNS queries succeed without a manual nmcli g reload or NM restart.

      ( ) Code changes are included in a downstream build attached to an errata.

      ( ) All required testing (manual and/or automated) passes successfully.

      ( ) Related documentation updates (if applicable) have been completed.

      ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified.

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given a host running NetworkManager with systemd-resolved or dnsmasq, and a DHCP lease that provides identical DNS servers but later changes the per-link routes those servers rely on, When NM processes the renewed lease, Then NM must regenerate the DNS configuration and the new reverse-DNS queries succeed without a manual nmcli g reload or NM restart. ( ) Code changes are included in a downstream build attached to an errata. ( ) All required testing (manual and/or automated) passes successfully. ( ) Related documentation updates (if applicable) have been completed. ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified.
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      Have proper reverse-DNS query forwarding set up.

      What is the impact of this issue to you?

      User experience.

      Please provide the package NVR for which the bug is seen:

      NetworkManager-1.53.4-1.el10

      How reproducible is this bug?:

      Often

      Steps to reproduce

      1. Retrieve new dns servers through DHCP
      2. Verify reverse-dns queries are forwarded to servers on the proper networks

      Expected results

      Forwarding works

      Actual results

      Forwarding works only after `# nmcli g reload`.

      More info

      bgalvani@redhat.com rightly pointed out that this issue is caused by hash function for DNS configuration not considering routes as DNS relevant information. We've agreed that i will try to fix this and refactor dns-manager code while doing so. This ticket serves as a RHEL tracker and i will add task for upstream implementation which i will assign to myself.

              nm-team Network Management Team
              tkorbar@redhat.com Tomáš Korbař
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: