Temporary failure in name resolution

There is no curl, no apt-get, no wget. These all return:
Temporary failure resolving 'mirrors.linode.com' or the likes

This really sounds like a firewall issue to me (but, then again, I'm not the Oracle at Delphi)…

Generally, an internet-connected server requires DNS… DNS operates over UDP but, in certain high-load/-throughput situations can offload to TCP. That's why both ports need to be open.

It's been my experience that an internet-connected server does not work very well (if at all) without port 53 being wide open. As mitigation for this (somewhat) obvious security hole, I restrict DNS traffic to/from Linode DNS servers only:

_dns = "{ 162.159.27.72, 162.159.24.39, 162.159.25.129, 162.159.26.99, 162.159.24.25 }"

_dns_6 = "{ 2400:cb00:2049:1::a29f:1a63, 2400:cb00:2049:1::a29f:1827, 2400:cb00:2049:1::a29f:1981, 2400:cb00:2049:1::a29f:1b48, 2400:cb00:2049:1::a29f:1819 }"

This seems to work well… However, YMMV.

-- sw

Save and reboot
 
Still I get the error!

Unless I'm mistaken, your changes to resolv.conf got overwritten by the Network Manager/Linode when you rebooted and you have "'Auto-configure networking' has applied".

How do I tell if the page https://chromedriver.storage.googleapis.com/97.0.4692.71/chromedriver_linux64.zip is able to receive this request?

I usually use curl…

Is there a way to test the nameservers?

dig (preferred) or nslookup (deprecated)…see man dig.

This works for me. Here's the traceroute output from my Linode in Fremont, CA:

traceroute to chromedriver.storage.googleapis.com (142.250.189.208), 64 hops max, 40 byte packets
 1  23.92.24.3 (23.92.24.3)  0.743 ms
    23.92.24.2 (23.92.24.2)  0.502 ms
    23.92.24.3 (23.92.24.3)  1.012 ms
 2  if-11-1-0-0.gw1.fnc1.us.linode.com (173.230.159.82)  3.687 ms
    if-0-1-5-0.gw1.fnc1.us.linode.com (173.230.159.66)  0.600 ms
    if-11-1-5-0.gw1.fnc1.us.linode.com (173.230.159.64)  2.228 ms
 3  ae0-100.gw2.fnc1.us.linode.com (173.230.159.9)  0.480 ms  0.514 ms
    213.52.131.177 (213.52.131.177)  1.383 ms
 4  * * *
 5  72.14.239.42 (72.14.239.42)  1.703 ms
    142.251.65.126 (142.251.65.126)  1.742 ms *
 6  209.85.247.54 (209.85.247.54)  1.643 ms
    142.251.224.173 (142.251.224.173)  1.575 ms
    72.14.239.42 (72.14.239.42)  1.527 ms
 7  66.249.94.29 (66.249.94.29)  2.418 ms
    72.14.237.147 (72.14.237.147)  1.844 ms
    216.239.62.41 (216.239.62.41)  1.952 ms
 8  74.125.253.150 (74.125.253.150)  2.189 ms
    142.250.234.55 (142.250.234.55)  2.564 ms
    sfo03s25-in-f16.1e100.net (142.250.189.208)  1.527 ms

-- sw

@stevewi

About:

Save and reboot

Still I get the error!

Unless I'm mistaken, your changes to resolv.conf got overwritten by the Network Manager/Linode when you rebooted and you have "'Auto-configure networking' has applied".

My response:
The option in the configurations 'Auto-configure networking' is off and that is confirmed. Maybe I fuddled it a couple times not too sure what was happening to the over-write but now that is past. I did the reboot after setting the configurations - Auto-configure networking to off so that when I edit sudo nano /etc/resolv.conf and reboot again there should have been no over-write. IDK, moving on! That setting sticks now and the over-writes happen no more.

I edit sudo nano /etc/resolv.conf with nameserver 8.8.8.8 so that I can test if it is the other nameservers or something different. Now, I still have the 'Temporary failure in name resolution' error. So I assume it is not the nameservers as 8.8.8.8 is google just the people who have the download I want from googleapis.

Now I will try wget on other linode see what happens.
Be back when I get done with that and a couple other attempts.

I appreciate the tip about dig and curl. curl was a second thought but I am hard-headed and want to know the answers to why before I move on unless I can afford no more time.

Just so you know I have edited the original post to try and make it clearer in case you read it again and see that it is different; I want you to know this.

My mistake… I thought I read that auto-configure was ON. Senior moment.

Does your firewall pass port 53 for both UDP and TCP?

For that matter, you prob should make sure your new DNS server accepts vanilla DNS and not just DNSSEC. Otherwise you’ll have to configure your Linode for both flavors.

— sw

@stevewi

There is an issue here which I do not know where I picked it up.
There is no curl, no apt-get, no wget. These all return:
Temporary failure resolving 'mirrors.linode.com' or the likes

I am gonna abandon this server and create a new one. It should not be too hard I have scripts to help.

I appreciate your time and help. This post is useless in light of the new information. If the new server acts the same way I will be able to break it down by script and figure it out at that time.

About your comment:
Does your firewall pass port 53 for both UDP and TCP?

I never had to think about it that way. When I create a server I have it locked down tight and ssh in on a disguised port. Only one way in while underdevelopment. The port 53 has never been allowed by any settings I have written and when I netstat or ss I have never see port 53 in any activity. When I create this new server I will pay attention to this port 53 but the thing is even after lock-down I was able to wget and apt-get and there are other services opening there own ports.

Again, I study a situation until I am out of time and now I have reached that moment when the decision to start over looks better that trying to be the pro.

Again, I really appreciate the your effort!

@stevewi

I had other issues with the previous server that I took into consideration before abandoning it. There were other things not resolved there.

When I created the new server I realised what had happened to the ufw port configuarion regarding DNS port 53. This should be cleared now.

Then, I totally disregared any consideration of a DNS server. It worked for a while for some reason and then it did not work for some reason. I am sure I may end up revisiting this question again in the future; but, that will be better when I have more time.

I learned a good lesson and am thankful for your help!