I'll chime in as well. This bug is absolutely ridiculous. I lost half a day to this.
I completely agree with Marten in 35:
> This is a blocking issue for non-technical users
I thought I had some nasty bug with my alexa to ngrok to django set up. Turns out, name lookups were just slow, causing my Alexa skill to time out. Once I figured out the cause, it was a 10m fix, but the hours of troubleshooting python packages to figure out the issue was just a waste.
Thank you to those of you who provided the details for the fix. Saved me a bunch of time.
To anyone that stumbles on this, I followed 8, 14 and 31 above, removing the file, relinking, and editing the systemd file to add a nameserver.
Here were my steps, YMMV:
sudo rm -f /etc/resolv.conf
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
sudo nano /etc/systemd/resolved.conf
then added the google nameservers to my file, adding this line.
nameserver 8.8.8.8
I'll chime in as well. This bug is absolutely ridiculous. I lost half a day to this.
I completely agree with Marten in 35:
> This is a blocking issue for non-technical users
I thought I had some nasty bug with my alexa to ngrok to django set up. Turns out, name lookups were just slow, causing my Alexa skill to time out. Once I figured out the cause, it was a 10m fix, but the hours of troubleshooting python packages to figure out the issue was just a waste.
Thank you to those of you who provided the details for the fix. Saved me a bunch of time.
To anyone that stumbles on this, I followed 8, 14 and 31 above, removing the file, relinking, and editing the systemd file to add a nameserver.
Here were my steps, YMMV: resolve/ resolv. conf /etc/resolv.conf resolved. conf
sudo rm -f /etc/resolv.conf
sudo ln -s /run/systemd/
sudo nano /etc/systemd/
then added the google nameservers to my file, adding this line.
nameserver 8.8.8.8
Good luck!