Fedora 37 dhcp-client-12:4.4.3-4.P1.fc37.x86_64 bind-chroot-9.18.13-1.fc37.x86_64 I am running a local caching name server. The last update to dchp-client hosed my networking. The new script does not pick up that I am running a local caching name server and decides to alter /etc/named.conf to something else. /etc/named.conf which is not a link Altered file: search netgear.com acme.local # netgear.com ?????? nameserver 192.168.250.1 # address of my gateway Should have left alone at: search acme.local nameserver 127.0.0.1 And it keeps changing it back !!!!! ; generated by /usr/sbin/dhclient-script search netgear.com acme.local nameserver 192.168.250.1 /etc/sysconfig/network-scripts/ifcfg-eno2 contains the following: BOOTPROTO=dhcp DNS1=127.0.0.1 Those are not picked up on either. Please fix this behavior. Many thanks, -T
Oops! bad: /etc/named.conf which is not a link good: /etc/resolv.conf which is not a link
This is kind of expected behavior in connection with your current setup, but there are a few ways to prevent /etc/resolv.conf to be overwritten though. The quickest solution is to modify /etc/resolv.conf as desired and then set 'i' attribute to it (this will prevent any modification to the file): ~~~ # chattr +i /etc/resolv.conf ~~~ One problem could arise if more people administrate your machine and they are not aware of this change (they could remove this attribute: chattr -i /etc/resolv.conf). Another possibility is to set 'PEERDNS=no' in /etc/sysconfig/network-scripts/ifcfg-eno2 if the resolv.conf should not be overwritten with the DNS servers obtained via DHCP: ~~~ PEERDNS=no ~~~ Besides /usr/sbin/dhclient-script the /etc/resolv.conf can be rewritten by NetworkManager itself and in that case, also the below should be set in /etc/NetworkManager/NetworkManager.conf and NetworkManager restarted afterward: ~~~ [main] dns=none ~~~ Otherwise, I can see you are still using the old way of configuring the network. I would recommend you to read this article: https://fedoramagazine.org/converting-networkmanager-from-ifcfg-to-keyfiles/
Hi Martin, Thank you for the tips. My network setup is complicated and it took me years to get everything working correctly. I am loath to try to redo everything over again. It also drives me a bit nuts with the troubleshooting when you guys change the behavior of things. My system was down most of the day fixing multiple things. My networking enables VPN's, fake adapters, internal and external networks, connect to a serial of virtual machines simulating a small business network (Samba, DHCP Server with fixed IP to MAC addresses, caching DNS which talks to DHCP server, etc.), including a very strong firewall. So far what I have seen with Network Manager is that is nice if you only have one network adapter, but it really does not help with my complicated setup. To work around the changes in behavior, I had to do the following: # nmcli device modify eno2 ipv4.dns "127.0.0.1" # nmcli connection modify "Wired connection 2" ipv4.ignore-auto-dns yes And then, I found out that `dhclient -r; dhclient` did not honor the above and updated my /etc/resolv.conf DNS to the DHCP Server's response for DNS anyway. Please fix that too. Fortunately both /usr/bin/nmcli connection up "Wired connection 2" /usr/bin/nmcli device up eno2 fixes dhclient's goof up. It took me three hours to trying figure out who was changing my resolv.conf back to DHCP's DNS and figure out that it was their call to calling dhclient. (It was my iptables script making sure I had the latest dhcp IP information before calling the tables.) My `PEERDNS=no` was commented out. I updated it. Many thanks, -T
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.