villelm
asked on
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 company.com newhost A 10.10.10.10 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.
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 company.com newhost A 10.10.10.10 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.
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
http://support.microsoft.com/?kbid=268674
No DNS Name Resolution If DHCP Client Service Is Not Running
http://support.microsoft.com/?kbid=268674
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 somedomain.com as an example you would add in this for Domain Integrated Zones:
Connection Point - Select or Type a Distinguished Name or Naming Context
DC=DomainDNSZones,DC=somed
Or for Forest Integrated Zones:
DC=ForestDNSZones,DC=somed
Expanding the MicrosoftDNS container in those should show all configured Zones (and the DNSNode's beneath). These two are the Application Partitions mentioned above.
Chris
ASKER
Thanks Chris! enabling scavenging and aging got me to the root of the problem. I appreciate the assistance.
You're welcome.
Chris
> 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.
Chris