Pi-hole FTL v4.2

How do I update my Pi-hole?

• How do I install Pi-hole?
• How do I test if my Pi-hole is working?
• How do I access my Pi-hole's Web interface?
• How do I use FTL's API?
• Why is FTL offline and showing "Lost Connection To API"?
• Where do I go for more answers?

See the Core changelog here

See the Web changelog here

New

• Update contained DNS server code to v2.80 #401
  Highlights:
  • Add support for RFC 4039 DHCP rapid commit.
  • Several bugfixes for DNSSEC.
    The Pi-hole team encourages you to play with DNSSEC when your upstream provider supports it.
  • Add a facilty to store DNS packets sent/recieved in a pcap-format file for later debugging.
  • Fix missing fatal errors with some malformed options.
  • Fix missing EDNS0 section in some replies generated by local DNS configuration which confused systemd-resolvd.
  • Implement --address=/example.com/# as (more efficient) syntactic sugar for --address=/example.com/0.0.0.0 and --address=/example.com/::.
    This feature has been suggested by the Pi-hole community.
  • Change anti cache-snooping behavior with queries with the recursion-desired bit unset. Instead to returning SERVFAIL, we now always forward, and never answer from the cache. This allows dig +trace command to work.
    This bug has been reported by the Pi-hole community.
• Add new NODATA blocking mode #433
• Use shared memory objects for data #429
• Use armv6 soft-float for the arm build - this enhances the compatibility with old ARM devices #468

Tweaks

• Mark queries imported from the database as having an unknown DNSSEC type #461
• Update SQLite to 3.26.0 #426
• Simplify upstream percentage computation #422

Fixes

• findQueryID(): Ensure indices are non-negative #470
• Gravity domains should not have REVERSE bit set #456
• Modify type of lastGCrun to avoid possible overflow #425
• Fix query status if forwarded query was partially replied to from cache #423