ubuntu:network:error:could_not_resolve
Differences
This shows you the differences between two versions of the page.
ubuntu:network:error:could_not_resolve [2020/08/19 14:49] – created 192.168.1.1 | ubuntu:network:error:could_not_resolve [2021/01/07 11:05] (current) – removed peter | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Ubuntu - Network - Error - Could not resolve ====== | ||
- | |||
- | If you get errors like this when you try to access something on the network, for instance when running " | ||
- | |||
- | <code bash> | ||
- | Err http:// | ||
- | |||
- | Err http:// | ||
- | Could not resolve ' | ||
- | |||
- | . . . | ||
- | </ | ||
- | |||
- | To fix, set your nameservers to outside nameservers. | ||
- | |||
- | <code bash> | ||
- | sudo vi / | ||
- | </ | ||
- | |||
- | Update the **dns-nameservers** line as shown: | ||
- | |||
- | <file bash / | ||
- | . . . | ||
- | iface eth0 inet6 static | ||
- | address 2604: | ||
- | netmask 64 | ||
- | gateway 2604: | ||
- | autoconf 0 | ||
- | dns-nameservers 8.8.8.8 8.8.4.4 | ||
- | </ | ||
- | | ||
- | Refresh your network settings: | ||
- | |||
- | <code bash> | ||
- | sudo ifdown eth0 && sudo ifup eth0 | ||
- | </ | ||
- | |||
- | |||
- | The expected output is: | ||
- | |||
- | Output | ||
- | |||
- | <code bash> | ||
- | RTNETLINK answers: No such process | ||
- | Waiting for DAD... Done | ||
- | </ | ||
- | |||
- | Next, create a new firewall rule to force IPv4 when it's available. | ||
- | |||
- | <code bash> | ||
- | sudo vi / | ||
- | </ | ||
- | |||
- | Add this single line to the file: | ||
- | |||
- | <file bash / | ||
- | Acquire:: | ||
- | </ | ||
- | |||
- | Save and close the file. Now you should be able to use APT. | ||
ubuntu/network/error/could_not_resolve.1597848542.txt.gz · Last modified: 2020/08/19 14:49 by 192.168.1.1