home.social

#coredns — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #coredns, aggregated by home.social.

fetched live
  1. DNS‑петля: как сервер смотрит сам в себя и не находит выхода

    Доменные имена не резолвятся, страницы висят, а по IP всё доступно. В логах DNS‑сервера при этом чисто, BIND запущен, конфигурация на первый взгляд выглядит рабочей. Разбираемся, как одна ошибка в forwarders может отправить DNS‑запросы по кругу и превратить обычный резолвинг в цепочку таймаутов.

    habr.com/ru/companies/otus/art

    #DNS #BIND #CoreDNS #forwarders #DNSпетля #systemdresolved #tcpdump #сетевая_диагностика #маршрутизация #таймауты

  2. I did a thing.
    github.com/coredns/coredns/rel
    #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

  3. Done.

    github.com/coredns/coredns/pul

    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

  4. #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.

  5. Ok. This the moment I stop using and maybe , for . 😎

    The implement of without me doing a single thing... Simply start the server... I don't think I need another dns authoritative server. 😉

    Excellent work from !

    blog.dnsimple.com/2026/02/erld

  6. 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 , which took about 2 hours to debug.

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

  7. 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.

  8. 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 (github.com/coredns/coredns/iss) 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 (github.com/coredns/coredns/pul) 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...?

    #linux #opensource #coredns

  9. 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, was an absolutely amazing source to learn from.

  10. TIL: #coredns #dnssec plugin only supports 3600s as TTL 😢

    > As the dnssec plugin can’t see the original TTL of the RRSets it signs, it will always use 3600s as the value.

    coredns.io/plugins/dnssec/

  11. Как service discovery ломается в Kubernetes (и почему DNS не всегда помогает)

    Привет, Хабр! В этой статье рассмотрим, как и почему в Kubernetes может сломаться service discovery — даже когда DNS вроде бы работает.

    habr.com/ru/companies/otus/art

    #kubertnetes #service_discovery #dns #coredns #kubeproxy