I did a thing.
https://github.com/coredns/coredns/releases/tag/v1.14.4
#coredns 1.14.4 Forward-plugin supports new `next_on_nodata` directive
When one upstream returns a NODATA response, itโ€˜ll then try the next forward plugin, instead of responding with NODATA itself.

#SelfHost #HomeLab

Release v1.14.4 ยท coredns/coredns

This release improves transport security and operational flexibility, with enhancements for DoH3 and DoQ, improved DNSSEC signing behavior, and support for the loong64 architecture. It also adds co...

GitHub
Miek Gieben released #CoreDNS version 1.14.4. https://coredns.io/
CoreDNS: DNS and Service Discovery

Celebrating #DigitalIndependenceDay with a foundational one: #DNS.

Every lookup travels unencrypted by default. Third-party #DoTโ€‹/โ€‹#DoH resolvers add encryption but shift trust elsewhere.

I run a self-hosted #CoreDNS resolver, handling this locally. Its plugin system enables #AdBlocking and delegation to upstreams like #PKDNS, which resolves names from the Mainline #DHT, offering self-sovereign, censorship-resistant #DNS.

https://di.day

#did #diday #didit #ididit #dut #dutgemacht

Home โ€” Digital Independence Day

On the first Sunday of each month we organise Digital Independence Day. This is when we reclaim our digital freedom and switch to democracy-friendly digital alternatives.

Done.

https://github.com/coredns/coredns/pull/8065

You have an authoritative #DNS server locally, and want to overwrite _some_ but not _all_ records? There you go. #CoreDNS 1.14.3 with this patch applied allows you to do exactly that.

Setup

*CoreDNS* Corefile:
. {
forward . RECURSOR {
next NOERROR
}
forward . UPSTREAM
}

*Recursor*, e.g. PDNS Recursor, with forward-zones-file content (or YAML equivalent):
+.=BIND9-IP

#OpenSource #Linux #HomeLab #SelfHost

plugin/forward: Forward NODATA responses to Next handler by AliveDevil ยท Pull Request #8065 ยท coredns/coredns

1. Why is this pull request needed and what does it do? Forward can't handle NODATA-responses, which are technically error responses as well. Using the NOERROR-case to allow forwarding to Next ...

GitHub

#CoreDns deprecated the "alternate"-plugin apparently - and I've relied on a patch I've made years ago to treat empty NOERROR-responses (colloquially known as NODATA) as errors, allowing for some naughty DNS hijacking.

Ported that code from years back to the in-tree "forward"-plugin. Going to verify that it works and propose the patch upstream. Hope it gets picked up this time.

Miek Gieben released #CoreDNS version 1.14.3. https://coredns.io/
CoreDNS: DNS and Service Discovery

Ok. This the moment I stop using #coredns and maybe #powerdns, for #erldns. ๐Ÿ˜Ž

The implement of #CodDel without me doing a single thing... Simply start the server... I don't think I need another dns authoritative server. ๐Ÿ˜‰

Excellent work from #dnsimple!

https://blog.dnsimple.com/2026/02/erldns-v10-release/?utm_source=dnsimple-changelog&utm_medium=banner&utm_campaign=whatsnew&utm_content333100

Building a Resilient Authoritative Nameserver

Announcing erldns v10, the authoritative erlang DNS server with CoDel queue management and improved congestion control.

Wow, CoreDNS is so easy to use and setup. Took me less than 5 minutes to install and configure it for forwarding dns requests to my Nebula lighthouse.

#coredns #nebula #nebulavpn #vpn #overlaynetworks

Today:

- There was an internet outage for about 5 hours.
- After which my home server froze (first Linux crash I've seen in a while).
- After force restarting it, somehow the Docker container networks changed so they broke one of my views for split-horizon DNS in #CoreDNS, which took about 2 hours to debug.

Breath in... breath out... breath in...

#SelfHosting #SelfHosted #HomeServer

Miek Gieben released #CoreDNS version 1.14.2. https://coredns.io/
CoreDNS: DNS and Service Discovery