Encrypted DNS from Boot to Runtime: A Zero Trust Milestone in RHEL
summary
RHEL adds system-wide encrypted DNS that works during installation, early boot and runtime by changing more than 10 components (Anaconda, dracut, OpenSSL, NetworkManager, dnsconfd, Unbound, Bind, FreeIPA, SSSD, Anaconda kickstart hooks, etc.) and shipping a local resolver so applications need no changes. It uses Unbound for DoT forwarding with a local port 53 cache and TLS to upstreams on port 853, accepts kickstart CA certs and kernel args, provides enforce/relaxed policies and plans DoH support.
AI-written summary · about
chapters (16)
- 0:00Encrypted DNS milestone intro
- 2:13DNS traffic privacy importance
- 7:12Zero trust architecture needs
- 9:03Encrypted DNS in RHEL needs
- 10:57System integration challenges
- 13:28Encrypted DNS protocols
- 15:56NetworkManager for encrypted DNS
- 17:19Install encrypted DNS
- 19:50IPA server with encrypted DNS
- 22:41Deploying IPA encrypted DNS
- 25:12Future DNS over HTTPS plans
- 27:24Q&A: Failover policies
- 30:39Q&A: Local caching options
- 33:00Q&A: BIND limitations
- 34:27Q&A: NetworkManager experience
- 35:31Closing remarks
related talks
01h 27mDNS at 30
25mProtective DNS, DNS Encryption, & Zero-Trust: Tackling NSA Guidance
34mUsing DNS as a layer of defense
37mUsing RHEL built in Security Technologies daily
46mDNSSEC
32mDNS as Added Security Against Ransomware Attacks
15mRHINE: Robust and High-performance Internet Naming with E2E Authenticity
43mBlock DNS exfiltration with dnsmasq proxy
