Sometimes when you try to ping a website, update your system, or perform a task that requires an active Internet connection, you may receive a temporary error message about resolving the name on your device.

For example, if you try to send a ping to a website, the error displayed may occur:

[Protected Email]:~$ ping
ping : : Temporary name failure

This is usually an error in resolving the name and indicates that your DNS server cannot resolve domain names to their respective IP addresses. This can be a serious problem because you cannot update, upgrade or even install software on your Linux system.

In this article we will look at some causes of the temporary naming error and how we can solve this problem.

1. Resolution filemissing or incorrectly configured

The /etc/resolv.conf file is the resolver configuration file for Linux systems. It contains DNS items that help your Linux system resolve domain names to IP addresses.

If this file does not exist, or if you still have a name resolution error, create it and add a Google Public DNS server, as shown in the following image

Name holder 8.8.8

Save the changes and restart the system authorized service as shown in the image.

$ sudo systemctl restart systemd-resolved.service

It is also useful to check the status of the resolver and ensure that it is active and functioning as intended:

$ state sudo sudo systemctl systemd-resolved.service

Try sending a ping to any website and the problem should be solved.

~$ ping

2. Firewall restrictions

If the first solution fails, firewall restrictions can prevent DNS queries from being successfully terminated. Check your firewall and make sure that port 53 (used for DNS – Domain name resolution) and port 43 (used for Whois searches) are open. If the ports are blocked, open them as follows:

For UFW Firewall (Ubuntu / Debian and Mint)

To open ports 53 and 43 on the UFW firewall, follow the commands below:

sudo ufw lets 53/tcp
$ sudo ufw lets 43/tcp
$ sudo ufw restart

For fire protection (RHEL / CentOS / Fedora)

For Redhat-based systems such as CentOS, use the following commands:

sudo firewall-cmd –add-port=53/tcp – persistent
$ sudo firewall-cmd –add-port=43/tcp – persistent
$ sudo firewall-cmd – reboot

We hope you now have an idea for a temporary name change and how to solve this in a few simple steps. As always, we welcome your comments.

If you like what we do here at TecMint, you should think:.

TecMint is the fastest growing and most reliable community site for all articles, guides and books about Linux on the web. Millions of people visit TecMint! to find or consult thousands of published articles that are accessible to everyone for FREE.

If you like what you read, consider buying us a coffee (or 2) as a thank you.

How to Resolve “Temporary failure in name resolution” Issue

Thank you for your continued support.temporary failure in name resolution aws,err name resolution failed ubuntu,composer temporary failure in name resolution,temporary failure in name resolution centos,temporary failure in name resolution java,linode temporary failure in name resolution,microk8s temporary failure in name resolution,rdate,fedora temporary failure in name resolution,scp temporary failure in name resolution,temporary failure in name resolution python,temporary failure in name resolution pihole,temporary failure in name resolution – raspberry pi,could not resolve hostname temporary failure in name resolution,temporary failure in name resolution kali linux,temporary failure in name resolution archlinux,temporary failure in name resolution virtualbox,ec2 temporary failure in name resolution

You May Also Like

How to Close Airtel Payment Bank Account Online & by SMS

Would you like to know how to close a bank account for…

Best Budget Fitness Tracker [Our Reviews and Comparisons]

Fitness trainers have become very popular. For some it is a status…

How to get unbanned from Tinder?

Like any online dating service, Tinder has a set of community guidelines…

Set Up Authentication & Authorization in Express Using JWT

Have you noticed that after logging in or connecting to Facebook through…