Anyhow, came back two days later, and only a very few number of machines have updated in forward dns represenative of Timestamp value changing from Static to an actual time. First off shouldnt they be updating now if the default update time for XP is 24 hours, and I have Dynamic updating on now???
If I run ipconfig /registerdns from any of the clients. There is no error any of the event logs (server or local) and the static entry in forward never updates. I noticed on each record that there is an account called Self with special permissions, yet when you drill down there are none set.
For AD Integrated Zones and Secure Only Updates: a.
ISC has made a note of the excessive traffic generated by Microsoft DNS servers configured with a single label name in 2004 with Microsoft, which in turn disabled the ability for Microsoft DNS in Windows 2000 SP4 and newer to resolve single label names without a registry band aid.
Two domain controllers also have a DHCP and DNS role.
Each DHCP server has the 'DNS dynamic updates registration credentials' setting populated with a user account which is a member of the 'Dns Update Proxy' group, and (although I've seen arguments for and against) I've added the servers themselves to the 'Dns Update Proxy' group.
The nios version is: 6.7.1-204398 I already have my dns zone (authoritative) with AD integration (svc entries & co.) and all works just fine.
For non-joined machines, it must be manually configured or scripted. If using DHCP Option 015 (Connection Specific Suffix), it must match the zone name and have "Use This Connection’s DNS Suffix in DNS Registration" along with "Register This Connection’s Addresses in DNS" checked in the NIC’s IPv4, Advanced, DNS tab. If the SOA is not available or resolvable, it won’t register.
If the machine’s DNS is statically configured: – It must only point to the internal DNS – It must be joined to the domain in order to authenticate using Kerberos to update. If statically configured and not joined to the domain, the client can’t update if the zone is set to Secure Only. For non-joined domain DHCP clients, you can configure DHCP to update in lieu of the client updating into a Secure Only zone. For any non-Windows statically configured machine, it must support the DNS Dynamic Updates feature and the zone configured to allow Secure and Unsecure updates. If the DNS server is multihomed and not configured properly to work with multihoming, it may cause problems with Dynamic Updates. If the zone is single label name, such as ‘domain’ instead of the proper minimal format of ‘domain.com,’ ‘domain.net,’ etc., it will NOT update. The client will "look" for the SOA of the zone when it attempts registration.
Archived from groups: microsoft.public.win2000(More info? )Server 2000 SP4 Domain Controller (bigorange.local)Active Directory integrated DNS (forward and reverse)Test Environment, not connected to the Internet Server 2003, NT 4.0 and XP Pro Clients (1 each)dcpromo created my dns and I deleted the root zone.
I created my reverse zone and added a forward zone bigorange.local - when I add computers to my domain, DNS is not updated with their IP address and hostname.