Microsoft DNS and non Microsoft clients

I know there is similar topics in the forum, but I can't solve my problem with those. Usually the answer is enable DNS dynamic updates in the DHCP server but, what if I want configure my clients with a fixex IP?

I have a domain with a lot of joined Windows PC working without problems. My domain controler is DHCP server and DNS server.

My problem is with other machines, one linux server (debian) and two iMac (osx 10.4). They can't resolve local dns names. They are unable to register in my DNS server. All of them have static IP address. What can I do? Must they have the domain name as sufix in their hostnames?

Thanks

October 29th, 2013 3:32pm

By default, all clients operating systems (Windows, Linux, Unix, etc etc etc), follow the industry standard RFCs for dynamic DNS registration. However, if the zone is set to Secure and Unsecure Updates, then non-joined machines will NOT be able to register because they must authenticate using Kerberos.

The default process is:
 1.By default, a Windows 2000 and newer statically configured machines will
register their A record (hostname) and PTR (reverse entry) into DNS. This applies to non-Microsoft operating systems, too.
2.If set to DHCP, a Windows 2000 or newer machine will request DHCP to allow
the machine itself to register its own A record, but DHCP will register its PTR
(reverse entry) record.
3.The entity that registers the record in DNS, owns the record.

To overcome that and have DHCP register all records, AND own the records  - In summary:
Configure DHCP Credentials. The credentials only need to be a plain-Jane, non-administrator, user account. Give it a really strong password.
Set DHCP to update everything, whether the clients can or cannot.
Add the DHCP server(s) to the Active Directory, Built-In DnsUpdateProxy security group. Make sure ALL other non-DHCP servers are NOT in the DnsUpdateProxy group. For example, some believe that the DNS servers or other DCs not running DHCP should be in it. They must be removed or it won't work.
On Windows 2008 R2 or newer, DISABLE Name Protection.
If DHCP is co-located on a Windows 2008 R2 or Windows 2012 DC, you can and must secure the DnsUpdateProxy group by running the following:
dnscmd /config /OpenAclOnProxyUpdates 0
Configure Scavenging one one DNS server. What it scavenges will replicate to others anyway. Set the NOREFRESH and REFRESH values combined to be equal or greater than the DHCP Lease length.

-

Specifics with screenshots:

This blog covers the following:
DHCP Service Configuration, Dynamic DNS Updates, Scavenging, Static Entries, Timestamps, DnsUpdateProxy Group, DHCP Credentials, prevent duplicate DNS records, DHCP has a "pen" icon, and more...
Published by Ace Fekay, MCT, MVP DS on Aug 20, 2009 at 10:36 AM  3758  2 
http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group.aspx  

Good summary
How Dynamic DNS behaves with multiple DHCP servers on the same Domain?
http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/e9d13327-ee75-4622-a3c7-459554319a27

Free Windows Admin Tool Kit Click here and download it now
October 29th, 2013 7:52pm

Hi Ace sorry for the delay and thanks for you reply.

This procedure, will it work with non-microsoft clients without DHCP, with static IPs? or Have I to change them to DHCP?

Thanks

November 5th, 2013 5:50am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics