ZimaOS no longer hardcodes Google DNS 8.8.8.8 into normal DNS configuration. The 2025 source bug came from the Thunderbolt network bridge code path, and the original reporter confirmed the unwanted entry was gone in ZimaOS 1.4.1.
On current ZimaOS, configure DNS per network interface under Settings → Network. If you still see 8.8.8.8 in /etc/resolv.conf, identify which NetworkManager connection or virtual interface supplied it before editing files by hand.
What Caused the Historical 8.8.8.8 Entry
IceWhale traced the entry to the system code used when creating a Thunderbolt network bridge. It was not meant to override every user's chosen DNS server.
The Bug Was Removed
The original reporter confirmed the extra 8.8.8.8 entry disappeared in ZimaOS 1.4.1. Current systems should not be treated as if this bug is still expected behavior.
Set DNS the Current Way
The current ZimaOS network configuration guide says to open Settings → Network, switch the interface to Manual when needed, and enter the desired DNS server.
Check the Effective Resolver
cat /etc/resolv.conf
nmcli device show | grep -i dns
nmcli connection showUse these as diagnostics. Do not make /etc/resolv.conf immutable or hand-edit generated NetworkManager files as the first fix.
Thunderbolt and Ethernet Can Have Different DNS Sources
If multiple interfaces are active, each connection can contribute DNS and route information. A direct Thunderbolt link and your normal Ethernet uplink should not be assumed to share one configuration.
Pi-hole or Technitium Users Should Test for Leaks
If all DNS is meant to pass through your local resolver, query the resolver logs and compare nmcli DNS values. A hardcoded fallback can bypass filtering, but so can DHCP or another active interface.
Do Not Block 8.8.8.8 Before Finding the Source
A firewall block may hide the symptom while leaving the wrong network profile configured. Fix the DNS source first; use firewall policy only if you intentionally enforce network-wide DNS.
The network troubleshooting guide provides broader network context.
DHCP Can Reintroduce a Different DNS Server
If an interface is left on DHCP, your router can supply DNS settings even after the old 8.8.8.8 bug is gone. When you need strict DNS control, compare the router's DHCP options with the DNS values shown by NetworkManager.
Manual DNS Changes Can Disconnect the Dashboard
When switching an interface from DHCP to Manual, verify IP, subnet, gateway, and DNS together. A wrong gateway or subnet can look like a DNS failure because the dashboard session may disappear immediately after saving.
Test Resolution Through the Intended Resolver
Use nslookup, dig, or your local DNS server logs to confirm queries are actually reaching Technitium, Pi-hole, or another chosen resolver. Do not judge only from the text in resolv.conf.
FAQ
Is 8.8.8.8 still hardcoded in ZimaOS?
The source reporter confirmed that historical entry was removed in 1.4.1.
Can I set my own DNS server?
Yes. Current ZimaOS Network settings support manual DNS per interface.
Should I edit resolv.conf directly?
No as the first step; it is typically managed by NetworkManager.
Why do I still see multiple DNS servers?
Check DHCP, multiple interfaces, Thunderbolt/virtual networks, and NetworkManager connection profiles.
