4 ms·
Huh, 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
by traverseda 9y ago
Huh, 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.