Hacker News new | past | comments | ask | show | jobs | submit login

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.




I 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.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: