If the service is stopped, DNS names will continue to be resolved.However, the results of DNS name queries will not be cached and the computer’s name will not be registered.Out came the smartphones, the conversation stopped, the food went cold and the beer warm.

ipconfig registerdns not updating dns-22

If the service is disabled, any services that explicitly depend on it will fail to start.

So the DNS Client is responsible for caching the results from the DNS Resolver, and register the computer’s FQDN in Dynamic DNS.

To be able to keep the forward and reverse zones in sync, the AD dynamic update message would also include updating the PTR records.

PTR records update would not be on by default and could be turned on by setting an option (perhaps For the update itself, we can simply use the nsupdate utility the way we use it in IPA domain.

In order to update the timestamp, the DNS records are refreshed periodically even if they actually haven’t changed, just to bump the timestamp.

A special timestamp value of 0 can be set to the resource record, indicating unlimited lifetime of the record. We will reuse a similar mechanism used in the IPA provider where the address used to connect to the AD server LDAP connection is used by default.

Clients enrolled to an Active Directory domain may be allowed to update their DNS records stored in AD dynamically.

At the same time, Active Directory servers support DNS aging and scavenging, which means that stale DNS records might be removed from AD after a period of inactivity.

So there was nothing for it: I went back to the hotel to do some testing. It is important to understand that we are talking about the DNS name resolution behavior here when the machine is acting as a DNS client, not a DNS Server.

Windows uses two components to resolve, register and cache DNS names. The DNS Resolver, aka the Windows resolver, is part of the TCP/IP protocol and cannot be disabled without disabling the protocol itself.

If you stop the DNS Client you can still resolve names, but they will not be cached and a DNS Server will be queried each time a name needs to be resolved to an IP address. Name resolution works the same for both Windows clients; XP, Vista, 7, 8 etc., and servers; 2003, 2008, 2008 R2, 2012.