Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

My network has a Windows machine running Server 2008 R2 which provides DHCP and DNS. I'm not particularly familiar with Windows domains, but the domain is set to home.local and that is the DNS domain name provided with DHCP leases.

Everything works fine for Windows machines, they get the lease and update the server with their hostname and the server creates a DNS records for windowshostname.home.local.

I am having problems obtaining the same functionality on Linux (Debian) and Mac OS X (Mountain Lion) machines. They receive DHCP just fine, but DNS entries are not being created on the server for them.

On the Mac OS X machine, hostname gives an output of machostname.local, and on the Linux machine hostname --fqdn also gives an output of linuxhostname.local. I'm assuming that the server is not creating DNS entries because the domain does not match that of the server (home.local).

I don't want to statically configure these machines to be part of the home.local domain, I just want them to pick it up from DHCP and be able to have entries in the DNS server. How should I go about doing this?

share|improve this question
Which version of OS X? Which Linux distribution(eg: Debian, Ububtu ..)? – John Siu Nov 10 '12 at 0:09
Is the server a Domain Controller and are the machines that work joined to that domain? How are you updating the records, using secure self-registered updates, or DHCP DNS update delegation? – MDMarra Nov 10 '12 at 0:10
@JohnSiu That information is available in the question. – DanielGibbs Nov 10 '12 at 0:13
@MDMarra Yes it is, most of the working machines are, but there is one Windows machine that is not joined to the domain that still successfully sends a dynamic DNS update to the server. I think it is using DHCP DNS update delegation. – DanielGibbs Nov 10 '12 at 0:14
On a Windows client there can be a primary DNS suffix and/or a connection specific DNS suffix. The primary DNS suffix is usually set when a Windows client joins a Windows AD domain (but can be set manually) while the connection specific suffix is set via DHCP (but it too can be set manually). What you're looking at appears to be the primary DNS suffix of the Linux and Mac computers. Can you look at the connection specific DNS suffix for the connection that's getting it's ip address via DHCP? – joeqwerty Nov 10 '12 at 17:38

I've managed to get it working on the Linux machine using the fix described here: In /etc/dhcp/dhclient.conf I added the line

send host-name "linuxhostname";

Still trying to find a Mac OS X equivalent though.

share|improve this answer

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.