Re: Dynamic DNS Issue
- From: "Todd J Heron" <todd_heron(delete)@hotmail.com>
- Date: Thu, 17 Nov 2005 22:32:47 -0500
"Az" <Az@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:69C0C3F8-E5B3-44DE-AC2E-069B994EF60E@xxxxxxxxxxxxxxxx
I upgraded NT 4.0 Domain to Windows 2003 AD and installed a DNS with the same name as AD. Configured the DNS to do a secure >DDNS update. All the memeber servers and clients are pointing to these new DNS Server for DNS resolutions. My clients are getting IP >via DHCP. After couple of days I noticed that the servers and clients are not updating their host names in the forward zone, even though >the reverse zone is updating correctly. I tried ipconfig /registerdns and it didn't worked. Then I tried configuring DHCP to updated DNS >and it didn't worked either. I tried removing one workstation from domain and rejoined it, the DDNS registration in the forward lookup >zone successed. Upon further investigation I noticed that the existing Clients have empty Domain entries in >the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" registry key, when I removed and joined >the machine to domain it populated the Domain entries with the Domain Name and the DDNS updates startrd working. We are running >Win2k3 sp1 as DCs\DNS and all the clients are XP Pro sp2. No policies are applied on the Clients. Since we have large number of client >machines it will not be possible for us to rejoin each of them to the Domain.
Conduct the following 7-point check:
1) External DNS servers are configured under TCP/IP properties. Only use internal DNS servers when part of an Active Directory domain. AD Domain machines must never be pointed at an external (ISP) DNS server or even use an ISP DNS server as an "Alternate DNS server".
2) AD/DNS zone not configured to allow dynamic updates.
3) 'Register this connection's address" in DNS is not enabled under TCP/IP properties.
4) Not authenticated to the domain (due to DNS misconfiguration or DNS server problem)
5) Missing or incorrect "Primary DNS suffix" or "Connection-specific DNS suffix" of the domain to which the machine belongs. With a missing/incorrect DNS suffix a machine cannot find the correct zone to register in.
6) A Group Policy is forcing secure updates and the machine isn't a member of the domain..
7) DHCP client service not running. This is a requirement for DNS registration and DNS resolution even if the client is not actually using DHCP. When this service is not running, the following error may result: "Registration of DNS records failed: The RPC server is unavailable." See the below two articles for more information.
No DNS Name Resolution If DHCP Client Service Is Not Running http://support.microsoft.com/default.aspx?scid=kb;en-us;268674
Dynamic DNS Updates Do Not Work if the DHCP Client Service Stops http://support.microsoft.com/default.aspx?scid=kb;en-us;264539
Note: DHCP can register the client in DNS, provided the DHCP server machine itself has the proper DNS servers set in it's TCP/IP properties.
-- Todd J Heron, MCSE Windows Server 2003/2000/NT; CCA ---------------------------------------------------------------------------- This posting is provided "as is" with no warranties and confers no rights
.
- Follow-Ups:
- Re: Dynamic DNS Issue
- From: Az
- Re: Dynamic DNS Issue
- Prev by Date: Re: Can view other servers on domain, but cannot access there resource
- Next by Date: Re: Can Ping FQDN but NOT Hostname without FQDN
- Previous by thread: Re: Can view other servers on domain, but cannot access there resource
- Next by thread: Re: Dynamic DNS Issue
- Index(es):
Relevant Pages
|
