{"id":4479,"date":"2022-12-10T09:04:57","date_gmt":"2022-12-10T09:04:57","guid":{"rendered":"https:\/\/arzhost.com\/blogs\/?p=4479"},"modified":"2023-10-16T19:46:13","modified_gmt":"2023-10-16T19:46:13","slug":"how-do-resolve-the-temporary-failure-in-name-resolution-issue","status":"publish","type":"post","link":"https:\/\/arzhost.com\/blogs\/how-do-resolve-the-temporary-failure-in-name-resolution-issue\/","title":{"rendered":"Resolve the \u201cTemporary Failure in Name Resolution\u201d Issue?"},"content":{"rendered":"<p>Sometimes when you try to ping a website, update a system or conduct any activity that requires an active internet connection, you may encounter the error message &#8216;How do Resolve the \u201cTemporary Failure in Name Resolution\u201d Issue? on your terminal.<\/p>\n<p><u>For instance, you can encounter the following error when attempting to ping a website:<\/u><\/p>\n<ul>\n<li>ping google.com arzhost@ubuntu<\/li>\n<li>Ping: Temporary name resolution failure for arzhost.com<\/li>\n<\/ul>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_74 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/arzhost.com\/blogs\/how-do-resolve-the-temporary-failure-in-name-resolution-issue\/#Resolve_the_%E2%80%9CTemporary_Failure_in_Name_Resolution%E2%80%9D_Issue\" >Resolve the \u201cTemporary Failure in Name Resolution\u201d Issue<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/arzhost.com\/blogs\/how-do-resolve-the-temporary-failure-in-name-resolution-issue\/#1_An_incorrectly_configured_or_missing_resolv_conf_file\" >1: An incorrectly configured or missing resolv. conf file<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/arzhost.com\/blogs\/how-do-resolve-the-temporary-failure-in-name-resolution-issue\/#2_Firewall_Limitations\" >2: Firewall Limitations<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/arzhost.com\/blogs\/how-do-resolve-the-temporary-failure-in-name-resolution-issue\/#1_Ubuntu_Debian_and_Mints_UFW_firewall\" >1: Ubuntu, Debian, and Mint&#8217;s UFW firewall<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/arzhost.com\/blogs\/how-do-resolve-the-temporary-failure-in-name-resolution-issue\/#2_Regarding_firewalld_RHEL_CentOS_and_Fedora\" >2: Regarding firewalld (RHEL, CentOS, and Fedora)<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Resolve_the_%E2%80%9CTemporary_Failure_in_Name_Resolution%E2%80%9D_Issue\"><\/span>Resolve the \u201cTemporary Failure in Name Resolution\u201d Issue<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This typically occurs when a domain name cannot be resolved into its corresponding IP address by your <a href=\"https:\/\/en.wikipedia.org\/wiki\/Domain_Name_System\" target=\"_blank\" rel=\"noopener\"><strong>DNS server<\/strong><\/a>. Since you won&#8217;t be able to update, upgrade, or even install any software packages on your Linux machine, this could pose a serious difficulty.<\/p>\n<p><iframe title=\"YouTube video player\" src=\"https:\/\/www.youtube.com\/embed\/u5DftRZJkmY\" width=\"560\" height=\"315\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n<p>We will examine some of the root reasons for the &#8220;<span style=\"color: #000000;\"><strong>How do Resolve the \u201cTemporary Failure in Name Resolution\u201d Issue?<\/strong><\/span>&#8221; error in this post, along with potential fixes.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"1_An_incorrectly_configured_or_missing_resolv_conf_file\"><\/span><strong>1: An incorrectly configured or missing resolv. conf file<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>At Linux systems, the resolver configuration file is located in \/etc\/resolv.conf. It includes the DNS records that your Linux system needs to convert domain names to IP addresses.<\/p>\n<p><u>Create a file and add the Google public DNS server as specified if this file is absent or present but you are still experiencing name resolution issues.<\/u><\/p>\n<ul>\n<li><code>8.8.8 is a name server.<\/code><\/li>\n<\/ul>\n<p><u>As demonstrated, save the modifications and restart the system-resolved service.<\/u><\/p>\n<ul>\n<li><code>restart system-resolved. Service with sudo systemctl<\/code><\/li>\n<\/ul>\n<p><u>It&#8217;s also a good idea to verify the resolver&#8217;s status to make sure it&#8217;s active and functioning as it should:<\/u><\/p>\n<ul>\n<li><code>$ sudo systemctl status system-resolved. Service<\/code><\/li>\n<\/ul>\n<p><u>After that, try pinging any website, and the problem ought to be resolved.<\/u><\/p>\n<ul>\n<li><code>ping google.com arzhost@ubuntu<\/code><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"2_Firewall_Limitations\"><\/span><strong>2: Firewall Limitations <\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In the event that the first option does not work for you, firewall constraints may be keeping you from correctly doing DNS queries. Check your firewall to see if ports 43 <u>(used for whois search) and 53 (used for DNS &#8211; Domain Name Resolution) are open. Open the ports as follows if they are closed:<\/u><\/p>\n<h3><span class=\"ez-toc-section\" id=\"1_Ubuntu_Debian_and_Mints_UFW_firewall\"><\/span><strong><u>1: Ubuntu, Debian, and Mint&#8217;s UFW firewall<\/u><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><u>Run the following commands to configure the UFW firewall to open ports 53 and 43:<\/u><\/p>\n<ul>\n<li><code>sudo ufw allow 53\/TCP for money<\/code><\/li>\n<li><code>UFW Allow 43\/TCP $ sudo<\/code><\/li>\n<li><code>Sudo ufw reload for $<\/code><\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"2_Regarding_firewalld_RHEL_CentOS_and_Fedora\"><\/span><strong><u>2: Regarding firewalld (RHEL, CentOS, and Fedora)<\/u><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><u>Use the following commands on Redhat-based systems, such as CentOS:<\/u><\/p>\n<ul>\n<li><code>$ Run firewall-cmd with a permanent add-port of 53 TCP.<\/code><\/li>\n<li><code>the command \"$ sudo firewall-cmd \u2014add-port=43\/TCP \u2014permanent\"<\/code><\/li>\n<li><code>firewall-cmd \u2014reload in sudo<\/code><\/li>\n<\/ul>\n<p>We hope you now have a better understanding of the &#8220;temporary failure in name resolution&#8221; error and how to quickly and effectively fix it. As always, I really value your input.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sometimes when you try to ping a website, update a system or conduct any activity that requires an active internet connection, you may encounter the error message &#8216;How do Resolve the \u201cTemporary Failure in Name Resolution\u201d Issue? on your terminal. For instance, you can encounter the following error when attempting to ping a website: ping [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":6199,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[66],"tags":[],"table_tags":[],"class_list":["post-4479","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-error"],"_links":{"self":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts\/4479","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/comments?post=4479"}],"version-history":[{"count":4,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts\/4479\/revisions"}],"predecessor-version":[{"id":8744,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/posts\/4479\/revisions\/8744"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/media\/6199"}],"wp:attachment":[{"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/media?parent=4479"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/categories?post=4479"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/tags?post=4479"},{"taxonomy":"table_tags","embeddable":true,"href":"https:\/\/arzhost.com\/blogs\/wp-json\/wp\/v2\/table_tags?post=4479"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}