#coredns — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #coredns, aggregated by home.social.
-
Miek Gieben released #CoreDNS version 1.14.6. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.6. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.5. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.5. https://coredns.io/
-
DNS‑петля: как сервер смотрит сам в себя и не находит выхода
Доменные имена не резолвятся, страницы висят, а по IP всё доступно. В логах DNS‑сервера при этом чисто, BIND запущен, конфигурация на первый взгляд выглядит рабочей. Разбираемся, как одна ошибка в forwarders может отправить DNS‑запросы по кругу и превратить обычный резолвинг в цепочку таймаутов.
https://habr.com/ru/companies/otus/articles/1051092/
#DNS #BIND #CoreDNS #forwarders #DNSпетля #systemdresolved #tcpdump #сетевая_диагностика #маршрутизация #таймауты
-
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. -
Miek Gieben released #CoreDNS version 1.14.4. https://coredns.io/
-
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 -
#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/
-
Miek Gieben released #CoreDNS version 1.14.3. https://coredns.io/
-
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...
-
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...
-
Miek Gieben released #CoreDNS version 1.14.2. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.2. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.1. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.1. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.0. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.14.0. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.13.2. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.13.2. https://coredns.io/
-
In lieu of "normal" dynamic #dns, I now have the following monstrosity:
1. #CoreDNS running in @flydotio (static IP and anycast UDP, naturally) with the JSON plugin, targeting a VPS
2. VPS running Caddy proxies the HTTP request from the JSON plugin to a VM running in my #homelab over a @tailscale subnet router
3. VM makes an HTTP request back to an app running on the VPS to get external IP
4. VM returns JSON formatted how the JSON plugin expects
5. VPS returns the proxied request back to CoreDNS running at Fly
6. CoreDNS caches the response and returns it to the requestor
Definitely won't regret this any time soon.
-
In lieu of "normal" dynamic #dns, I now have the following monstrosity:
1. #CoreDNS running in @flydotio (static IP and anycast UDP, naturally) with the JSON plugin, targeting a VPS
2. VPS running Caddy proxies the HTTP request from the JSON plugin to a VM running in my #homelab over a @tailscale subnet router
3. VM makes an HTTP request back to an app running on the VPS to get external IP
4. VM returns JSON formatted how the JSON plugin expects
5. VPS returns the proxied request back to CoreDNS running at Fly
6. CoreDNS caches the response and returns it to the requestor
Definitely won't regret this any time soon.
-
Miek Gieben released #CoreDNS version 1.13.1. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.13.1. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.13.0. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.13.0. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.12.4. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.12.4. https://coredns.io/
-
Recently I wanted to migrate my home infra from blocky to CoreDNS. As I use DoH I researched if CoreDNS supports it, and stumbled upon a (sad) story.
A couple years ago one user created an issue (https://github.com/coredns/coredns/issues/4147) about lacking of DoH support. Another user in the thread mentioned that there is a community need and offered help. Maintainer replied "maybe it's because we all volunteers here?". This user created PR (https://github.com/coredns/coredns/pull/4583) that implements it. Some time later, after a couple of minor code review comments, maintainer closed PR without sensible justification... You can read attached links and form your own opinion. I know that only one side of this conflict had spoken, but isn't this silence meaningful?
How as an open-source community can we expect that people will help if we treat them like that...?
-
Decided to switch my local DNS server from a hosts file configuration to a real RFC 1035 configuration because I needed wildcard records, and I learned so much. As always, #Wikipedia was an absolutely amazing source to learn from.
#DNS #SelfHost #SelfHosting #SelfHosted #HomeServer #CoreDNS
-
Decided to switch my local DNS server from a hosts file configuration to a real RFC 1035 configuration because I needed wildcard records, and I learned so much. As always, #Wikipedia was an absolutely amazing source to learn from.
#DNS #SelfHost #SelfHosting #SelfHosted #HomeServer #CoreDNS
-
Miek Gieben released #CoreDNS version 1.12.3. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.12.3. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.12.2. https://coredns.io/
-
Miek Gieben released #CoreDNS version 1.12.2. https://coredns.io/
-
Как service discovery ломается в Kubernetes (и почему DNS не всегда помогает)
Привет, Хабр! В этой статье рассмотрим, как и почему в Kubernetes может сломаться service discovery — даже когда DNS вроде бы работает.
-
Как я перестал страдать и полюбил CoreDNS: три истории
Всем привет! Я Саша Краснов, CTO контейнерной платформы «Штурвал». В апреле прошла юбилейная DevOpsConf 2025, на которой мне посчастливилось выступать с докладом. Рассказывал я про хаки, которые позволяют автоматизировать использование DNS. Эта статья построена на базе моего доклада и трех реальных историй: — управление DNS из git; — собственный nip.io ; — как и зачем писать плагины для CoreDNS. Приходите под кат, там интересно :) Попасть под кат
https://habr.com/ru/companies/chislitellab/articles/913946/
#coredns #dns #kubernetes #k8s #nipio #git #github #плагины #штурвал #devops
-
Hmmm, it seems like my websites appearing as down in Kener (or is it kener.ing ?) is because my coredns instance cannot solve the DNS request ?
But I'm thinking, Longhorn has also shown, for a long time, dropped requests when rebuilding big volumes...
Could it be, my wireguard under the hood dropping packages ? Hmmmmmm...
#homelab #selfhosted #longhorn #wireguard #kener #dns #coredns #k3s #kubernetes #k8s
-
-
Miek Gieben released #CoreDNS version 1.12.1. https://coredns.io/
-
I currently use #NextDNS and #CoreDNS for my DNS needs. I set up CoreDNS to log out somewhere so I can see DNS queries, set it up so prometheus can pull stats on it, and make sure I feel dope about it! I never looked at that shit once. Just set up dns forwarding to #nextdns on this router and it's working just fine with a couple of A records for internal shit..
I just shut down my #coredns stuff.. All the times I create just to delete later.
-
So I was able to accomplish split-dns with #nextdns and #coredns . If you are on the tailnet you use nextdns which points you to the tailnet ip's if you are internal you use #coredns that points you to stuff internally.
Technitium handled this easier.. It just lends it's self really heavy to webui stuff. -
Effortlessly deploy and manage your #DNS zones across private and public networks with DNSimple On-Premise Deployments with #coredns
Visit for more details: https://www.youtube.com/watch?v=9yO2Oo_N1ms -
#coredns is apparently incapable of listening on link-local IP addresses making my hopes that any VM could find its DNS on fe80::53 futile.