3 ms·
On the other hand, it improves safety and security for many users. Because on most distros, using unbound or BIND9 as local DNS server, they bind to all interf
by kuschku 9y ago
On the other hand, it improves safety and security for many users.
Because on most distros, using unbound or BIND9 as local DNS server, they bind to all interfaces, publicly.
Which is the reason why DNS amplification DDoS even is possible.
I’ve seen it often enough happen, and basically every person who’s set up their own servers has made the mistake of leaving the defaults.
- jeltz 9y agoOn Debian, and I assume its derivates, Unbound will by default only listen to localhost. What distribution has changed this, because I think that is also the upstream default?
- kuschku 9y agoUbuntu 14.04 and Debian old-old-stable listened on all interfaces. The versions provided by most cloud hosters are also misconfigured to listen on all interfaces.
- jeltz 9y agoHm, as far as I can tell Debian has never shipped a version which listens to something other than localhost by default. The upstream fixed this in 2007, before Debian started packaging Unbound.
- lottin 9y agoBut who runs a DNS server? 99% of users only do DNS resolution and for that you don't need to run a DNS server on your system.
- kuschku 9y agoMany people run a DNS server to cache DNS responses locally. And they don’t want to expose the DNS server publicly. systemd-resolved does that, you can’t even expose it accidentally. But many distros actually install a DNS server by default, usually unbound or BIND9, and while some bind it to localhost, many bind it to all interfaces. As you said, that’s not necessary for most users, yet, major distros do it.
- deleted 9y ago[deleted]
- pgl 9y agoWhich distros install a DNS server (and enable it) by default? I've never seen this.
- deleted 9y ago[deleted]
- barrkel 9y agodnsmasq has been installed as a local DNS cache on Ubuntu and other Debian derivatives for many years. /etc/resolv.conf normally points at localhost.
- deleted 9y ago[deleted]
- dsp1234 9y agoIt only listens on localhost though (127.0.1.1 by default), so it's not possible for it to be abused for dns amplification attacks.
- dom0 9y agoIIRC dnsmasq still listens on all interfaces for some reason
- afuchs 9y agoI thought DNS was connectionless? Don't all DNS clients have to bind to UDP port 53 to function correctly?
- smhenderson 9y agoIt's not the port that matters; it's the interface. A caching DNS service for a simple desktop experience should only be listening for queries on the localhost interface (lo).
- feld 9y agoThis has nothing to do with this conversation. DNS recursors are not being discussed. This is strictly about DNS resolvers.
- JdeBP 9y agoEvery person who has followed my and Daniel J. Bernstein's recommendations when setting up their own servers will not have done any such thing. We have been giving these recommendations for the better part of two decades now. * http://jdebp.eu./FGA/proxy-server-ip-addresses.html http://jdebp.eu./FGA/proxy-server-ip-addresses.html * http://cr.yp.to/djbdns/run-cache.html http://cr.yp.to/djbdns/run-cache.html