Upgrading to 22.10 breaks resolv.conf

@jaybo, you say "I do not want a fixed DNS", but from your discussion, you actually do. Without it, you end up with DNS entries 172.98.193.42 and 198.206.14.241, which do not work for you.

In your other post, you mention when your system is working properly, your DNS setting is

DNS Servers: 192.168.1.1

You say you are using Network Manager. Per my final comment in the bug report, with Network Manager, I got the system to behave consistently by putting the proper DNS entries into Network Manager, separately for each configured interface. From the system menu, select System -> Preferences -> Internet and Network -> Advanced Network Configuration. Then, for you primary connection (mine is Ethernet -> Wired connection 1), highlight it and then click the edit icon on the bottom. On the IPv4 Settings tab (use IPv6 Settings if that is applicable to you), under DNS servers, add in the appropriate values for your DNS servers. For me, this is

192.168.2.1, 1.1.1.1, 1.0.0.1

The first is my router, and the next two are CloudFare, the public DNS servers I prefer. I don't know if this is strictly required, but my thinking was that if the router DNS entries get corrupted, I can fall back to CloudFare. I have these same CloudFare DNS servers configured in the router.

In your case, you would enter the 192.168.1.1 value. Let me know if you still have questions, and I will post pictures of my Network Manager configuration to show where I entered the DNS entries.

1 Like