<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - systemd-resolved 213 adds extra dns servers even when dns from dhcp is supplied" href="https://bugs.freedesktop.org/show_bug.cgi?id=79672#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - systemd-resolved 213 adds extra dns servers even when dns from dhcp is supplied" href="https://bugs.freedesktop.org/show_bug.cgi?id=79672">bug 79672</a> from <a class="email" href="mailto:radek@podgorny.cz" title="Radek Podgorny <radek@podgorny.cz>"> Radek Podgorny</a> <pre>yes, setting DNS= is what i've been using so far to work-around it but it simply feels wrong. when my network is configured correctly (dhcp sending resolvers), i see no reason to add arbitrary (why google's 8.8.8.8?) servers to resolv.conf. also, when something breaks, i think it would be better to get to notice as soon as possible instead of having seemingly weird behaviour (1). as for the "fallback", the resolv.conf also supports the 'rotate' option (see man resolv.conf) which changes the behaviour to be round-robin. i can't even imagine how stressful debugging broken resolver would be in such case. i totally understand having sane defaults for non-auto-configured systems (virtual machines, ...) but let's not interfere with centrally driven network configuration (dhcp). (1): as an example: windows machines would stop working but linux one won't. or even better, some linux machines will fail because they're not systemd-based. also, ever more delicate things may start to happen (dnssec, site-local resolution, ...).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>