home.social

#coredns — Public Fediverse posts

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

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

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

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

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

    blog.dnsimple.com/2026/02/erld

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

    blog.dnsimple.com/2026/02/erld

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

    blog.dnsimple.com/2026/02/erld

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

    blog.dnsimple.com/2026/02/erld

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

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

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

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

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

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

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

  17. In lieu of "normal" dynamic , I now have the following monstrosity:

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

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

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