3 ms·
> I switched to Arch right after the systemd transition, so I'm sure I missed a big opportunity for breakage. I experienced that transition and while you had t
by AsyncAwait 9y ago
> I switched to Arch right after the systemd transition, so I'm sure I missed a big opportunity for breakage.
I experienced that transition and while you had to read the wiki somewhat carefully, I remember being a bit 'disappointed' afterwards as to how smooth/uneventful it was, it sounded way more scary than it actually was.
- saimiam 9y agoWell, just yesterday, I had to go back a release from Ubuntu 17.04 to 16.04 because of some oscure DNS related systemd-resolved bug which I spent all day trying to fix. Mind you, this bug has been under active discussion for a while now. Since my 16.04 server is just a day old now, I'm thinking I'll bite the bullet and switch to a troublefree distro recommended in this thread. (Not a Linux cognoscenti.)
- traverseda 9y agoHuh, I had to do the same thing yesterday. Interesting coincidence. Did you add DNSSEC=no to /etc/systemd/resolved.conf? That fixed the problem I had yesterday, which is probably a different problem.
- saimiam 9y agoI did but that didn't work for me. Btw, were you on a Linode in a southern US city? - I changed DNSSEC to NO. - I had DNSmasq running which was apparently blocking systemd-resolved from binding to 127.0.0.1.53#53. I first changed dnsmasq's port to 5300 from 53 and then killed dnsmasq but that didn't solve the issue either. 3. I manually linked resolv.conf to a non standard location which I hand edited to contain the name servers I wanted my server to use - didn't work.