Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've seen multiple default configurations of DHCP-servers with a FQDN set as the DNS-server option. Doesn't this imply a catch-22, or the need for that DNS-server to be in the hosts file of every single client?

example from dhcp3-server in debian 6:
option domain-name-servers;

I can see how using a dns name is convenient because it's only an A-record to change, and they can be load balanced if wanted, but I don't see how the client is going to resolve the name.

Why are people using FQDN's as DNS-server addresses in DHCP?

share|improve this question
up vote 2 down vote accepted

The server should resolve the name then sent the resultant IP to the client.

share|improve this answer
Ofcourse! Why didn't I think of that? – Filip Haglund Jun 24 '13 at 16:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.