~/talk

CoreDNS Deep Dive

slides:none on file

Tests use CoreDNS with the erratic plugin inside Docker to truncate every third UDP reply and a small Go client to run net.LookupHost; glibc retries truncated answers over TCP and honors EDNS0 buffer increases, Go also falls back to TCP, while musl ignores TCP and stays stuck on UDP so AAAA lookups can fail. Using Kubernetes resolv.conf with ndots=5 causes many extra queries (up to 6×); CoreDNS autopath reduces that. Recommendation: prefer Debian-slim or static Go binaries and use fully qualified names with a trailing dot.

AI-written summary · about

  1. 0:00Introduction
  2. 1:44Stub-resolver basics
  3. 3:06Testing stub-resolvers with CoreDNS
  4. 6:37RFC TCP requirements
  5. 8:44resolv.conf format
  6. 11:56libc implementations comparison
  7. 14:00ndots impact on Kubernetes DNS
  8. 17:16FQDN importance
  9. 19:00OS choice for Docker
  10. 21:24DNS dot handling issues
  11. 22:48DNSSEC and local caching
  12. 24:16CoreDNS Go migration
  13. 25:41Go DNS socket usage
  14. 26:44Linux race conditions in DNS
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.