OT: Recently, I had to learn systemd-resolved likes to take control of port 53 t... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		arendtio on March 20, 2019 \| parent \| context \| favorite \| on: How to take back control of /etc/resolv.conf on Li... 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

yrro on March 20, 2019 [–]

Doesn'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 on March 20, 2019 | [–]

Yes, 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).

Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact