Windows 2008 - DNS - Conditional Forwarders and DNS Cache

[shadow_man]

Hey

Is there any way to disable DNS cache for conditional forwarders?

e.g. I don't want AD to cache anything for those entries.

I only want it to query an external DNS server if the condition is met but I don't then want it to cache that reply, as I update DNS frequently and caching screws me around.

Example:

Currently:

PC queries mydomain.com > conditional forwarder for mydomain.com > external dns server based on conditional forwarders rule > entry gets cached.

NOW if I change an entry on the external DNS server for the cached record i'm in trouble as it still returns the cached item to workstations, hence I need to STOP this.

So I want:

PC queries mydomain.com > conditional forwarder for mydomain.com > external dns server based on conditional forwarders rule > NO CACHING and if any workstation queries this item again its forced to go through the forwarder and check the IP again due to no cache being present?

Any help would be great. DNS in Windows is severely lacking...

Kapish?

 

[@udiS3]

Flush the active directory cache after you have made your changes:
>ipconfig /flushdns

Even if you disable caching on the AD server you still have the issue of cached DNS entries on client machines from recent queries! DNS clients are designed to maintain a cache to improve network performance.

Why are you updating DNS frequently? Are your servers not set with static IP address?
Are you trying to load balance?

http://support.microsoft.com/kb/305967

 

[shadow_man]

Flush the active directory cache after you have made your changes:
>ipconfig /flushdns

Even if you disable caching on the AD server you still have the issue of cached DNS entries on client machines from recent queries! DNS clients are designed to maintain a cache to improve network performance.

Why are you updating DNS frequently? Are your servers not set with static IP address?
Are you trying to load balance?

http://support.microsoft.com/kb/305967

Thanks.

I'm already doing ipconfig /flushdns on the DC (interesting to note that clearing cache in the GUI doesn't seem to have the same effect)...

I'm part of a dev shop and I setup DNS as soon as the dev's have new VM's they've spun up - so DNS is constantly changing for the local items, hence updates needs to be QUICK and RELIABLE.