3 ms·
OT: Recently, I had to learn systemd-resolved likes to take control of port 53 too. For me, this was a problem when I wanted to run a DNS server [1] on that por
by arendtio 8y ago
OT: Recently, I had to learn systemd-resolved likes to take control of port 53 too. For me, this was a problem when I wanted to run a DNS server [1] on that port, to be able to request wildcard certificates from Letsencrypt without using the API of my Domain Provider.
[1] https://github.com/joohoi/acme-dns https://github.com/joohoi/acme-dns
- yrro 8y agoDoesn't it only bind to 127.0.0.53? That wouldn't get in the way of another nameserver unless you also wanted it to bind to the same address...
- arendtio 8y agoYes, that is right. Binding the DNS server to the public IP address only was the workaround I choose at the time, but I had to configure it explicitly (default was 0.0.0.0).