A couple of Linode's DNS resolvers are timing out -- what's the big deal?

Hey there! The first - and quickest - solution we typically recommend in this case is to make sure you have our Network Helper feature enabled -- this feature will attempt to configure your Linode's networking configuration files upon boot, and make sure your Linode's /etc/resolv.conf file is up to date.

Keep in mind, however, that Network Helper will only run successfully if your Linode is running a Linode-supported image -- Linux distributions such as CloudLinux or Devuan are not compatible with Network Helper.

If our automatic network configuration feature can't resolve the issue for whatever reason, you can always manually edit your Linode's /etc/resolv.conf file to make sure the resolvers are up to date. Your Linode's resolvers are:

66.228.42.5

96.126.106.5

50.116.53.5

50.116.58.5

50.116.61.5

50.116.62.5

66.175.211.5

97.107.133.4

207.192.69.4

207.192.69.5

2600:3c03::5

2600:3c03::6

2600:3c03::7

2600:3c03::8

2600:3c03::9

2600:3c03::b

2600:3c03::c

You can use Google's public resolvers as a replacement, or as an addition, to Linode's DNS resolvers:

8.8.8.8

8.8.4.4

The IP addresses listed above are for resolvers in the Newark data center. Every data center Linode has comes with their own set of resolvers. If you would like to see the resolvers for the data center your Linode is in, they can viewed them through Linode Manager.

Cloud Manager:

In your Linode's Networking section:

DNS Resolvers (IPv4): 66.228.42.5 (+9)

Clicking on the +9 will reveal the additional resolver IPs.

Classic Manager:

In your Linode's Remote Access section, there is list next to DNS Resolvers

In addition to Google' Open Resolver, you could also use Cloudflare's Public Resolver:

4.4.4.4