This is not only a Linux issue – <https://www.ionos.com/digitalguide/hosting/technical-matters/err-name-not-resolved-error/>.
[HR][/HR]Please, please, please, ignore all the information you may possibly find, indicated that, you should use Alphabet and/or Google as your DNS provider.
- The reason why can be found if, you search carefully in the wonderful library know as the Internet.
Ditto, information indicating that, you should use the IPv4 address ‘8.8.8.8’ to point to the Name Servers …
[HR][/HR]Please, please, please, setup your machine to use DHCP to pull the address or addresses of the Name Servers from the IP Router connected to your Internet Service Provider –
- In other words, simply trust your ISP …
The ‘/etc/resolv.conf’ file should look something like this –
### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
search fritz.box
nameserver 192.168.178.1
nameserver fd00::5e49:79ff:fedc:e1aa
Please note that, it ain’t a physical file – it’s a link pointing to a system generated file located in memory – ‘/var/run/netconfig/’.
- As the generated text states – setup your DNS by using parameters in the file ‘/etc/sysconfig/network/config’ …
- And then issue the command “netconfig update -f
” from the user “root” to bring any changes made into the current running system.
As an example, my settings for the relevant network configuration parameters are as follows:
NETCONFIG_DNS_STATIC_SEARCHLIST="fritz.box"
NETCONFIG_DNS_STATIC_SERVERS="192.168.178.1"
NETCONFIG_DNS_FORWARDER="resolver"
NETCONFIG_DNS_POLICY="auto"
Set the static search list to the local private network name of the Router you’re using to access your ISP.
The local private address of the Router is possibly “192.168.178.1” or, some other private IPv4 address …
- If the Router connecting your machine to your ISP doesn’t have a DNS functionality then, point the above settings to the device within your local network which is providing the DNS for you local network.
You’ve mentioned that, you’re a business user and, therefore, the bullet above may well be the case for your situation.
[HR][/HR]Back to the root cause –
- As “IONOS” (an absolutely tiny ISP here in Germany which is a part of “United Internet” – also absolutely tiny – only 10 thousand employees and more than a few server centres – the largest with only 25 thousand servers
) are mentioning –
Restart the Router.
Clear the cache of the Chrome Browser.
Clear the DNS cache of your system – with the user “root”, issue the command “systemctl restart nscd.service”.
Disable the predictions the Chrome Browser would prefer to use …