Windows 2000 DNS without DHCP

My question is two parts really. I have a Windows 2000 AD environment. Almost all clients are statically IP'd, though there are a few DHCP clients out there but not many. I just noticed that the DNS records in my DNS servers don't necessarily match up with the true records for a number of desktops. As desktops have been replaced over time, the process to name them and keep the same old IP address was lax.
 Correct me if I am wrong, but it would appear to be that XP & Win2kPro desktops do NOT dynamically update their DNS entry if they are statically IP'd. From what I have read so far, you need them to be using DHCP for addressing, and then it should work. So first part of the question is, I am right or wrong with this paragraph?
 Assuming I am right, I thought of creating a more automated method to update the DNS server entries to match the real values on the client. I was thinking of having a script to ping a machine, then run the 'hostname' command on it. Then I would take the correct IP and hostname and use the DNSCMD command to create the proper entry. In theory, I don't see why this shouldn't work.
 However, the DNSCMD errors out on me every time, from my Domain Controller/ DNS server itself. (actually from both of my DNS servers).
 Starting simply, from an RDP on the DNS server, I try:
 dnscmd . /Info   which gives Command Failed: Unknown 1717
 dnscmd hostname_of_dns_server gives same error 1717
 dnscmd IP_of_dns_server /Info  gives same but error 1753
 Further commands such as:
 dnscmd . /RecordAdd newhost A   give me the same errors above, depending on the entry for my DNS server, either a 1717 or 1753 error.
 It would appear that the DNS command fails when communicating to the DNS server. Clearly, doing these commands on the DNS server itself shouldnt be an issue. Is there some configuration or Group Policy setting that would block this? I am beginning to think I somehow misconfigured integrated AD-DNS.
 Any help would be appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris DentPowerShell DeveloperCommented:

> Correct me if I am wrong, but it would appear to be that XP & Win2kPro desktops do NOT
> dynamically update their DNS entry if they are statically IP'd.

You're wrong :)

Confirm that Dynamic Updates is turned on and set to Secure Only.

On a workstation run "ipconfig /registerdns" then check the Event Log for DNSAPI error messages.

In addition to that it would be sensible to configure Aging and Scavenging on the zones so they keep themselves clean.

I have the same problem as the poster. I have it set up to do Secure Updates Only on the DNS servers. Ipconfig /registerdns didn't seem to do anything. At least it didn't create a new value when I deleted the old one. I need to check the event viewer. I was reading on Microsoft's site and it says.
The following components perform DNS updates:
•Dynamic Host Configuration Protocol (DHCP) Client service
These updates apply to all Windows 2000-based computers.
•DNS Server service
These updates apply to Windows 2000-based DNS servers only.
•Net Logon service
This updates apply to Windows 2000-based domain controllers only.
•Remote access client
These updates apply to Windows 2000-based remote access clients only.

Now, if I read that right, DHCP does the DNS updating. If a host is using Static IP's, is the DHCP service still involved to do the updating?

Are you positive hosts not using DHCP will update DNS on a Windows 2000 DNS server?
Chris DentPowerShell DeveloperCommented:

Yes, I'm positive.

It works like this. If DHCP is enabled and explicitly told to update DNS on the clients behalf then it will and the clients ability to update is disabled.

The DNS client, and the DNSAPI that comes with that has the ability to dynamically register records within DNS. This kind of functionality is essential for the smooth operation of an AD Domain (or at least the smooth operation without every admin requiring an intensive course in DNS).

The option in DHCP is generally considered a legacy option, it is there to ensure that Windows NT and 9x machines (or anything else that doesn't support Dynamic Updates) can get a DNS record.

To date I only know of a few instances where Dynamic Updates completely fails:

1. DNS Service was installed on Windows NT which was subsequently upgraded to Windows 200x.

A tricky one to solve since it's very difficult to completely remove a Windows component and install it again. Generally advisable to move the service to a server that hasn't been upgraded.

This may not apply in every case.

2. DNS Zone is corrupt.

The zone should be cleared out of AD and completely recreated. The instructions for this are here for Windows 2000:

That also covers 2000 upgraded to 2003 as the upgrade process doesn't move the DNS zone from the Directory Partition to it's own separate Application Partition where Windows 2003 prefers such things.

3. Client Settings say not to.

Open up the registry editor and check for an adaptor specific registry setting:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Interface name>\DisableDynamicUpdate

If the value exists and is set to 1 Dynamic Updates will not occur.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ON-DEMAND: 10 Easy Ways to Lose a Password

Learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees in this on-demand webinar. We cover the importance of multi-factor authentication and how these solutions can better protect your business!

You might have the DHCP Client service disabled; this service is necessary for the dynamic updates, so do NOT disable it (yes, even when using static IP addresses).
No DNS Name Resolution If DHCP Client Service Is Not Running
Chris DentPowerShell DeveloperCommented:

Oops, forgot a bit.

If you happen to need to clear an AD Integrated Zone out using a Windows 2003 Domain then you would open ADSIEdit.msc. Select "Connect To" then, if we use the AD Domain Name as an example you would add in this for Domain Integrated Zones:

Connection Point - Select or Type a Distinguished Name or Naming Context

Or for Forest Integrated Zones:


Expanding the MicrosoftDNS container in those should show all configured Zones (and the DNSNode's beneath). These two are the Application Partitions mentioned above.

villelmAuthor Commented:
Thanks Chris!  enabling scavenging and aging got me to the root of the problem.  I appreciate the assistance.
Chris DentPowerShell DeveloperCommented:

You're welcome.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.