But what about GP's point regarding mirrors? Your IP will be transmitted to potentially a wide range of effectively 3rd party hosts. Looking at my /var/log/dnf.librepo.log I can see requests from a number of hosts, including:
I never explicitly agreed to connect to all of these hosts (some are from repos I did manually enable), and it wasn't made abundantly clear to me during install they would be used. As far as trying to keep GDPR hygiene up, I don't see why this is better than configuring a default DNS server if you're worried about IP address transmission.
There's a huge difference between disclosing your IP and disclosing all the various websites you visit. Moreover, those websites are being disclosed to entities whose commercial business is to track you--for marketing, for performance, w'ever.
Relatedly, your IP is also disclosed via NTP. NTP hosts can be advertised over DHCP, similar to DNS resolvers. And systemd also has built-in fallbacks for NTP, which has actually caused major headaches working on security compliance for U.S. government services because the instances should never use any NTP server other than time.nist.gov. But if time.nist.gov is unavailable for w'ever reason, systemd by default falls back to non-compliant NTP hosts. Disabling this is tricky if you rely on DHCP-advertised NTP servers (which is preferable to minimize the diff between govcloud and non-govcloud deployment images).
