Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 copy of Bug #2218448

Description of problem:

 After reconnecting a device, the order of name servers in resolv.conf is wrong

 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1331

Version-Release number of selected component (if applicable):

 All NM versions from 1.32 to 1.43.10.

How reproducible:
 100%

Steps to Reproduce:
 nmcli connection add type dummy con-name dummy-dummy1 ifname dummy1 \
                      ip4 172.25.1.1/24 gw4 172.25.1.254 ipv4.dns 172.25.1.53 \
                      autoconnect no ipv4.route-metric 100 ipv6.method disabled
 nmcli connection add type dummy con-name dummy-dummy2 ifname dummy2 \
                      ip4 172.25.2.1/24 gw4 172.25.2.254 ipv4.dns 172.25.2.53 \
                      autoconnect no ipv4.route-metric 200 ipv6.method disabled

 nmcli connection up dummy-dummy1
 nmcli connection up dummy-dummy2

 # now dummy1 is best

 nmcli connection down dummy-dummy1

 # now dummy2 is best

 nmcli connection up dummy-dummy1

 # due to the bug, now both dummy1 and dummy2 are best

 cat /etc/resolv.conf

Actual results:

 The first name server is 172.25.2.53 in resolv.conf

Expected results:

 The first name server is 172.25.1.53 because dummy1 has the best default route

Additional info:

 Upstream fix: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1683

Closing as this is already fixed upstream.