What kind of issues would occur if resolve.conf had no dns servers set?

Stuart Woodward asked:

I want to create a server for a customer and have that customer finish the configuration for themselves. It was been decided that rather than setting default DNS servers (i.e. something like Google’s) that the customer should enter the information by themselves. I assume that the customer is technically competent enough to do this.

If however they forget or neglect to set this up they might spend some time trying to figure out what is wrong and eventually contact support. (In this case, I think that setting a default might have been better.)

Apart from the obvious inability to resolve hosts, what other issues might they face until they have set valid dns servers in resolve.conf?

My answer:


Not being able to resolve hosts is the issue they’ll face.

This means they won’t seem to have Internet connectivity and will get strange errors like:

Temporary failure in name resolution

which don’t necessarily lead non-technical users to check /etc/resolv.conf.

If at all possible, and these are meant to be turnkey systems, configure your servers with default entries such as those provided by Google Public DNS:

nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844

View the full question and answer on Server Fault.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.