Windows 2003 DHCP/DNS server and non-Windows clients

Usually, in a 100% Microsoft environment, DHCP that automagically updates the DNS entries for every new DHCP client in the network is not a problem, since every client is part of the Active Directory and every machine as by default the rights to “talk” to the DNS server and tell it which is the client’s new IP address and hostname.

But if you have other clients in your network (for example Linux, FreeBSD, embedded devices like JetPrint etc) that need DHCP and you want automatic DNS update, this will not work because they don’t have the rights to write in the DNS records list.

To solve this problem, the update has top be done by the DHCP server itself, and to do the trick you have

  • Go to an AD user management snap-in
  • Create a new user called, for example, dhcp2dns and make it member of the DnsUpdateProxy group
  • Give a password to the dhcp2dns user
  • Go to the DHCP snap-in, and select the server you want to configure
  • Right click on the server name /address, and select properties
  • Here, select the DNS tab
  • Tick the Enable DNS dynamic updates checkbox
  • Select Always dynamically update DNS A and PTR records
  • Now, select the “Advanced” tab and click the “Credentials” button
  • Here, put the credentials of the dhcp2dns user you have created in the first steps

and you are done, it should work or, at least, it did work for me :)


10 thoughts on “Windows 2003 DHCP/DNS server and non-Windows clients

  1. Thanks a lot. I have read so many hints and documents on the net to get this to work, but to no use.
    Your tip worked right away. :-)

  2. @Leonardo: it should be the same, although I didn’t try (only XP SP2 here). If you can give it a try and let me know the result, I’d update the post for sure :)

  3. It should work with Windows 2000 but not using the same exact option set. No user authentication is available, but there are buttons to allow updates for non-Windows clients and turn on auto update of DHCP.

  4. Can someone try to explain how exactly this will work?
    I am not sure if i understand it.
    When dhcp assign ip to non-windows client what will happen next?
    dhcp2dns will know about this and will update dns? or what?

  5. […] just found this: Windows 2003 DHCP/DNS server and non-Windows clients May be useful for the DNS issue. Maybe not so much for the problem of not being able to log in. […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s