Temporary failure resolvingerror on Ubuntu 20.04 Focal Fossa Linux
In this tutorial you will learn:
- How to check current DNS server
- How to how to internet connection
- How to query DNS name
Software Requirements and Conventions Used
|Category||Requirements, Conventions or Software Version Used|
|System||Installed Ubuntu 20.04 or upgraded Ubuntu 20.04 Focal Fossa|
|Other||Privileged access to your Linux system as root or via the
# - requires given linux commands to be executed with root privileges either directly as a root user or by use of
How to fix Temporary failure resolving error on Ubuntu 20.04 step by step instructionsIf you get stuck at any of the below points try to resolve them before continuing, as each step might provide you with hints on how to fix your original
Temporary failure resolvingerror.
- Although this error message is most likely related to the DNS server name resolution, the first step is to check our internet connection. To do so execute the following
$ ping -c 2 188.8.131.52 PING 184.108.40.206 (220.127.116.11) 56(84) bytes of data. 64 bytes from 18.104.22.168: icmp_seq=1 ttl=54 time=10.4 ms 64 bytes from 22.214.171.124: icmp_seq=2 ttl=54 time=10.2 ms --- 126.96.36.199 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1006ms rtt min/avg/max/mdev = 10.157/10.291/10.425/0.134 msThe above command should result in
0% packet loss.
- Check your DNS server network configuration settings:
$ systemd-resolve --status | grep Current Current Scopes: DNS Current DNS Server: 192.168.1.1Our system is set to use DNS server host with an IP address
- Next, make sure that you can reach your DNS server. Again, the
pingis a handy tool also here:
$ ping -c 2 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.535 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.570 ms --- 192.168.1.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1016ms rtt min/avg/max/mdev = 0.535/0.552/0.570/0.017 msThe output of the above command should result in
0% packet loss.
In case you cannot reach your DNS it could mean that it either, does not respond to ping's ICPM packages, it is behind the firewall or the server is down. In which case update your
/etc/resolv.confwith an alternative DNS server.
- Test you DNS server by attempting to resolve DNS name eg.
$ dig @192.168.1.1 linuxconfig.org ; <<>> DiG 9.11.5-P4-5.1ubuntu4-Ubuntu <<>> @192.168.1.1 linuxconfig.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21662 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;linuxconfig.org. IN A ;; ANSWER SECTION: linuxconfig.org. 300 IN A 188.8.131.52 linuxconfig.org. 300 IN A 184.108.40.206 ;; Query time: 408 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Wed Dec 11 14:02:07 AEDT 2019 ;; MSG SIZE rcvd: 76
Confirm system-wide settings by trying to resolve DNS host name. Example:
$ resolvectl query linuxconfig.org linuxconfig.org: 220.127.116.11 -- link: enp0s3 18.104.22.168 -- link: enp0s3 -- Information acquired via protocol DNS in 2.7ms. -- Data is authenticated: no